[DRAFT] feat: [UIE-9051] - IAM RBAC block non-beta route access

[corya-akamai]

Description 📝

Block non-beta users from the IAM screens and redirect to the account screens accordingly. Redirect beta users from the account screens to the IAM screens respectively.

Changes 🔄

• Block non-beta users from the IAM screens and redirect to the account screens accordingly.
• Redirect beta users from the account screens to the IAM screens respectively.

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 🗓️

Preview 📷

How to test 🧪

Prerequisites

• Devcloud IAM account
• Devcloud non-IAM account

Reproduction steps

Navigate to routes

• /iam/users <-> /account/users
• /iam/roles <-> (no equivalent) /account/users
• /iam/users/corya-iam/details <-> /account/users/corya-iam/profile
• /iam/users/corya-iam/roles <-> /account/users/corya-iam/permissions
• /iam/users/corya-iam/entities <-> /account/users/corya-iam/permissions

Verification steps

Verify redirect

• /iam/users <-> /account/users
• /iam/roles <-> (no equivalent) /account/users
• /iam/users/corya-iam/details <-> /account/users/corya-iam/profile
• /iam/users/corya-iam/roles <-> /account/users/corya-iam/permissions
• /iam/users/corya-iam/entities <-> /account/users/corya-iam/permissions

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

[abailly-akamai]

@corya-akamai see #12644 for an alternative handling of redirects at the route definition level, which may be what we want

[linode-gh-bot]

Cloud Manager UI test results

🔺 3 failing tests on test run #2 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
3 Failing	702 Passing	4 Skipped	131m 10s

Details

Failing Tests
	Spec	Test
❌	qemu-reboot-upgrade-notice.spec.ts	Cloud Manager Cypress Tests→QEMU reboot upgrade notification » should display maintenance banner in 'Linode' landing page when one or more Linodes get impacted.
❌	timerange-verification.spec.ts	Cloud Manager Cypress Tests→Integration tests for verifying Cloudpulse custom and preset configurations » should implement and validate custom date/time picker for a specific date and time range
❌	linode-storage.spec.ts	Cloud Manager Cypress Tests→linode storage tab » delete disk

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/notificationsAndEvents/qemu-reboot-upgrade-notice.spec.ts,cypress/e2e/core/cloudpulse/timerange-verification.spec.ts,cypress/e2e/core/linodes/linode-storage.spec.ts"