hotfix: [UIE-9134] Increase page size for RBAC IAM entities call

[abailly-akamai]

Description 📝

The v4beta/entities API cannot be filtered currently, and this causes some accounts with larger numbers of entities to not see some entities in the results, which are used in various UI elements like autocompletes. Increasing the page size to 500 (the max) will help delay for a real solution.
Note: the v4beta APIs do not support X-Filter at the moment, so this is just a temporary workaround.

Changes 🔄

List any change(s) relevant to the reviewer.

• The v4beta/entities API call should now request a page size of 500.
• In some cases, as shown below, this means that entities that were not available are now seen.

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

August 26

Preview 📷

Before	After

How to test 🧪

Prerequisites

• Use IAM account with role assignment permissions

Reproduction steps

• Navigate to IAM > Roles
• Click Assign Role next to an entity role, such as "VPC viewer" to open the assignment drawer
• Notice that no VPCs are available to assign if the account has >> 100 (page size) entities (this may take some effort)
• Filtering on entities does not help since the API call is not going to be made again

Verification steps

• Navigate to IAM > Roles
• Click Assign Role next to an entity role, such as "VPC viewer" to open the assignment drawer
• Notice that now some VPCs are available to assign if the account has < 500 (page size) total entities
• Filtering on entities still does nothing - the only change was the page size

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

[bill-akamai]

Verifying changes ✅

[jdamore-linode]

Just confirming the test failure isn't related to this PR's changes (see also M3-10514)

[mjac0bs]

✅ Thank you!

[mjac0bs]

Since this is going to staging, we don't need this changeset. @bill-akamai Do you want to update the changelog directly?

[abailly-akamai]

Can't we keep them? They seem relevant staging or not? (sorry i don't remember what the best course is for staging fixes)

[mjac0bs]

Changesets have already been deleted and translated to changelogs at this stage in the release process. Agreed that this change is relevant to document! Best course is just to update the changelog, but if we don't want to dismiss reviews on this PR, that can also be done on the staging branch directly.

[bill-akamai]

Yes @alioso - can you update the changelog directly rather than adding the changeset(s)?

[abailly-akamai]

Oh! of course i'll do that

[bill-akamai]

Thanks @abailly-akamai !

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #4 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	734 Passing	4 Skipped	123m 13s

Details

Failing Tests
	Spec	Test
❌	object-storage-objects-multicluster.spec.ts	Cloud Manager Cypress Tests→Object Storage Multicluster objects » can upload, access, and delete objects

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/objectStorageMulticluster/object-storage-objects-multicluster.spec.ts"