feat: [UIE-9357] - IAM Delegation: Default Roles table

[mpolotsk-akamai]

Description 📝

This PR adds the Default Roles table for Default Access.

Changes 🔄

List any change(s) relevant to the reviewer.

• Update AssignedRolesTable
• Update Change/Unassign Role drawers

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

11/04

Preview 📷

How to test 🧪

Prerequisites

(How to setup test environment)

• IAM parent/child DevCloud account (IAM Delegation (Parent/Child) flag should be enabled)
• use MSW CRUD mode

Verification steps

(How to verify changes)

• go to /iam/roles/
• click 'View default roles' button
• go to 'Default Roles' tab
• verify that table with default roles is visible

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]

UI looks good! and logic is mostly good and in sync with the entities tab.

Approving pending some cleanup and code quality improvements.

[abailly-akamai]

same comment as above. This can all be cleaned up since the useIsDefaultDelegationRolesForChildAccount is used in all those modals

[aaleksee-akamai]

@abailly-akamai , could you please check if that's what you mean? I haven't found anything similar to this in CM (might've missed something)

[abailly-akamai]

This works but I would simplify: (sorry the enabled suggestion was not appropriate/needed)

conditional queries/mutations are tricky to handle. usually we tend to render different components but I think this should suffice.

Maybe i am overthinking this and username ?? '' is fine but either way the challenge is to surface a proper error if that happens. Usually i try to prevent sending a mutation if we already know the payload isn't right. sending '' is just getting around the types which isn't ideal

export const useUserRolesMutation = (username: string | undefined) => {
  const queryClient = useQueryClient();

  return useMutation<IamUserRoles, APIError[], IamUserRoles>({
    mutationFn: (data) => {
      if (!username) {
        throw new Error('Username is required');
      }
      return updateUserRoles(username, data);
    },
    onSuccess: (role) => {
      if (username) {
        queryClient.setQueryData<IamUserRoles>(
          iamQueries.user(username)._ctx.roles.queryKey,
          role,
        );
      }
    },
  });
};

[mpolotsk-akamai]

Updated, thanks!

[linode-gh-bot]

Cloud Manager UI test results

🔺 3 failing tests on test run #12 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
3 Failing	844 Passing	12 Skipped	41m 33s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	Cloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page
❌	create-firewall.spec.ts	Cloud Manager Cypress Tests→create firewall » "before all" hook for "creates a firewall without a linode"
❌	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

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts,cypress/e2e/core/firewalls/create-firewall.spec.ts,cypress/e2e/core/cloudpulse/timerange-verification.spec.ts"