upcoming: [UIE-9740] - Implement Lock/Unlock feature in Linode Landing and detail action menu.

[tanushree-akamai]

Description 📝

This PR implements the display of Lock/Unlock action in action menu for Linodes. The feature is gated behind a feature flag (resourceLock.linodes)

Changes 🔄

• Added ResourceLockFlag to featureFlags
• Added lock permissions to IAM types:
  • AccountAdmin: create_lock, list_locks, view_lock, delete_lock
  • AccountViewer: list_locks, view_lock
• Updated LinodeActionMenu to show Lock/Unlock actions
  • Only visible when resourceLock feature flag is enabled
  • Disabled with tooltips when user lacks permissions

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

Preview 📷

1. Added ResourceLockFlag to featureFlags
   Before
   
   After
   

2. Updated LinodeActionMenu to show Lock/Unlock actions

3. Added lock permissions to IAM:

|

How to test 🧪

Reproduction steps

• Open DevTools Panel
• Enable the Resource Lock feature: Find resourceLock -> linodes ->Toggle to true
• In DevTools Panel, navigate to "MSW" section
• Enable CRUD mocks: Toggle "Enable MSW" to ON -> Select "CRUD" preset
• In DevTools Panel, navigate to "Seeds" section -> Set seed counts: Linodes: 10, Resource Locks: 5
• Navigate to "User Permissions" section
• Select "Custom User Account Permissions"
• Click "Edit" to modify permissions
• Update the permissions array to include lock permissions:
  [ "create_lock", "delete_lock" ]
• Click on Apply

Verification steps

• Navigate to /linodes
• Confirm Lock/Unlock action appears in Linode list and detail action menu
• Verify Permission-Based Behavior:
• With full permissions: Action is enabled (clickable)
• Without permissions: Action is disabled with a tooltip showing "You don't have permission to edit this Linode"
• Lock Status Display:
• Linodes with locks show "Unlock" action
• Linodes without locks show "Lock" action

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 #2 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	864 Passing	11 Skipped	35m 13s

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"

[grevanak-akamai]

Shouldn't we look for lockData using useLockQuery as this GET call should be for individual linode item?