upcoming: [UIE-9837] - Generational plans changes for Databases

[hana-akamai]

Description 📝

Update Database Create and Resize tables to support generational plans changes

Note: I will remove the hardcoded json before merging

Changes 🔄

• Display Generational Plan changes in Databases similar to Linodes when G7 plans are available and disable the Premium tab in Database Create and Database Resize (non-premium cluster)
• Adjust resize logic (see verification steps below)
• Minor refactoring
• Remove legacy code around resizing 2-node clusters

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

4/29/26

Preview 📷

See demo attached in internal ticket

How to test 🧪

Prerequisites

(How to setup test environment)

• Checkout this PR locally, and follow the verification steps

Verification steps

(How to verify changes)

• If G7 plans are not present in dbtypes, there should be no changes to the Database Create or Resize plan tables
• Simulate G7 plans by commenting out the dbtypes query and uncommenting the hardcoded dbtypes around line 88 in DatabaseCreate.tsx and around line 96 in DatabaseResize.tsx
• If G7 plans are present in dbtypes and UI LD flag databaseResizeGenerationalPlans is OFF:
  • Database Create:
    • Similar display to Linode Create.
    • Show Dedicated Plans and Types dropdowns in the Dedicated CPU tab and show “Select a region to view plans and prices” placeholder in the Plan table.
    • Premium CPU tab is disabled with tooltip that Premium plans are now G7 Dedicated plans.
  • Database Resize:
    • Show Dedicated Plans and Types dropdowns in the Dedicated CPU tab.
    • If the cluster is NOT a premium plan:
      • G7 plans are not displayed under All Available Plans option. Under All Plans option, G7 plans are disabled.
      • Premium CPU tab continues to be disabled.
    • If the cluster IS a premium plan:
      • Premium CPU tab continues to be enabled. Shared CPU tab continues to be disabled.
      • Dedicated CPU tab is enabled. Only G7 plans are shown under All Available Plans option. Under All Plans option, Non-G7 Dedicated Plans are disabled.
• G7 plans are returned in /databases/types endpoint and UI LD flag databaseResizeGenerationalPlans is ON:
  • Database Create:
    • No change to OFF state, same as above.
  • Database Resize:
    • G7 plans are displayed and enabled under All Available Plans option regardless of whether the current plan is premium or not.
    • Cross resizing plans is possible (Shared -> G7 Dedicated/Premium, G7 Dedicated/Premium -> Shared, etc)

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

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	901 Passing	11 Skipped	41m 43s

Details

Failing Tests
	Spec	Test
❌	object-storage.e2e.spec.ts	Cloud Manager Cypress Tests→object storage end-to-end tests » can update bucket access

Troubleshooting

Use this command to re-run the failing tests:

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

[smans-akamai]

Note: As mentioned in the description, the dbtypes json file that mocks the new response in Database Create and Resize will be removed along with references to it in the code like the line above prior to merging.

[smans-akamai]

Do we not need typesError and typesLoading?

[smans-akamai]

It looks like these were just removed for the mock data. Planning to add the checks these were used in back before merging the pull request. See related comment for context.

[smans-akamai]

Same question that I had in DatabaseCreate. Were these just removed temporarily for testing with mock data? If so, we should probably ad this back along with adding them to the loading state condition.

[smans-akamai]

After looking over the code, it looks like these were just moved temporarily, so we'll plan to add these back to the loading state when we remove the temporary database types json file and testing code.