upcoming: [M3-7951] Update Placement Groups region API limits #10343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description 📝
This PR brings CM up to date with the latest region limits ALPHA deployments. This update's only concern is updating the GET region limits API response to match the expected shape.
becomes:
It enables the UI to properly handle PG limits. Limits are currently set with hard coded values on the API side, so the behavior is predictable for now:
5
max PGs per Customer5
max Linodes per PGChanges 🔄
Preview 📷
How to test 🧪
Prerequisites
pg-user-1
(1Password)Verification steps
As an Author I have considered 🤔
Check all that apply