upcoming: [DI-28270] - Remove firewall filtering and region filter dependency

[ankita-akamai]

Description 📝

Remove firewall filtering and region filter dependency in Firewalls.

Changes 🔄

• Update filterConfig.ts to remove linode-region and nodebalancer-region filter dependency on firewall/firewalls select.
• Update filterConfig.ts to remove filtering of firewalls visible in firewall-select based on associated entity types, e.g. linode/nodebalancer.
• Update CloudPulseRegionSelect.tsx to remove region filtering based on firewalls selection.
• Update test cases.

Scope 🚢

Upon production release, changes in this PR will be visible to:

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

Target release date 🗓️

16 Dec 2025

Preview 📷

Before	After

How to test 🧪

Verification steps

(How to verify changes)

• Navigate to metrics page under monitor.
• Select Cloud Firewall for Linode dashboard.
• Verify that linode-region filter is enabled irrespective of firewall selection.
• Click on firewalls dropdown, all firewalls in the account will be listed
• Select a firewall.
• Click on region dropdown, verify that all aclp supported regions are visible.
  Note: Regions whose region Obj in /regions api call has monitors: ['Cloud Firewall'] capability are considered aclp supported.
• Select a region.
• Verify that metrics can be visualized if there is data available.

Now, go to dashboard-select again.

• Select Cloud Firewall for nodebalancer dashboard.
• Verify that nodebalancer-region filter is enabled irrespective of firewall selection.
• Click on firewalls dropdown, all firewalls in the account will be listed
• Select a firewall.
• Click on region dropdown, verify that all aclp supported regions are visible.
  Note: Regions whose region Obj in /regions api call has monitors: ['Cloud Firewall'] capability are considered aclp supported.
• Select a region.
• Verify that metrics can be visualized if there is data available.

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

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #3 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	861 Passing	11 Skipped	41m 31s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	Cloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"

[ankita-akamai]

Merging as the pr has enough approvals and failing test is unrelated.