upcoming: [UIE-9640] – Update useIsFirewallRulesetsPrefixlistsEnabled to include account capability check - #13156
Conversation
…FirewallRulesetsPrefixlistsEnabled() to check for that capability
Cloud Manager UI test results🔺 19 failing tests on test run #2 ↗︎
Details
TroubleshootingUse this command to re-run the failing tests: pnpm cy:run -s "cypress/e2e/core/linodes/linode-storage.spec.ts,cypress/e2e/core/databases/create-database.spec.ts,cypress/e2e/core/volumes/upgrade-volume.spec.ts,cypress/e2e/core/linodes/resize-linode.spec.ts,cypress/e2e/core/linodes/linode-config.spec.ts,cypress/e2e/core/volumes/delete-volume.spec.ts,cypress/e2e/core/images/machine-image-upload.spec.ts,cypress/e2e/core/images/smoke-create-image.spec.ts,cypress/e2e/core/volumes/attach-volume.spec.ts,cypress/e2e/core/firewalls/migrate-linode-with-firewall.spec.ts" |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
pmakode-akamai
left a comment
There was a problem hiding this comment.
Changes look good!
It's un-related, but the only concern I have is the rulesets will not appear in the /rulesets API, but the references are still showing up in the firewalls/:id API when customer tag is removed. I feel that these references should not appear in the API at all. This is something the API team may need to fix, but I'm not sure.
@pmakode-akamai Yes, that's something that should be addressed at the API level I believe. It could pose issues for other consumers of the API too (Terraform, etc.). |
|
The E2E failures all look to be related to the pipeline issues rather than any PR changes, so I'm going ahead and merging. |

Description 📝
Update
useIsFirewallRulesetsPrefixlistsEnabledto include account capability checkChanges 🔄
Cloud Firewall Rule Setto AccountCapability typeuseIsFirewallRulesetsPrefixlistsEnabled()to include account capability checkScope 🚢
Target release date 🗓️
December 2025
How to test 🧪
Prerequisites
Firewall RuleSets and Prefix Listshas itsenabledandbetaflags onVerification steps
Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed ✅