Tech story: [UIE-8943] - Replace dropdowns in Database cluster settings page with CDS select web component

[grevanak-akamai]

Description 📝

This PR is to replace dropdowns in Database cluster settings page with CDS select web component.

Changes 🔄

• Replaced day and time dropdowns under weekly maintenance section in database cluster settings page with CDS select Web Component.

Target release date 🗓️

N/A

Preview 📷

Before	After

How to test 🧪

Prerequisites

• Go to Databases -> DB cluster details page -> Settings tab
• Under "Set a Weekly Maintenance Window" section, verify select "day of week" and "time" dropdowns.

Verification steps

• Dropdowns under "Set a Weekly Maintenance Window" section in DB cluster settings page should work same as before. All the validations should behave the same.

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

[dwiley-akamai]

When I first load the page and try to select a time, there's a pretty odd UI bug I'm observing on this branch that doesn't happen in prod:

Screen.Recording.2025-11-06.at.2.11.16.PM.mov

[dwiley-akamai]

Could arguably be a Tech Story since it's not really a change impacting the look/feel or functionality for the user

[jaalah]

Apart from the navigation issue, this looks 👍

[grevanak-akamai]

When I first load the page and try to select a time, there's a pretty odd UI bug I'm observing on this branch that doesn't happen in prod:

Screen.Recording.2025-11-06.at.2.11.16.PM.mov

I'm not able to replicate this issue in local though I see it in PR preview link. Can you pull the latest code and test it again in local?

[dwiley-akamai]

When I first load the page and try to select a time, there's a pretty odd UI bug I'm observing on this branch that doesn't happen in prod:
Screen.Recording.2025-11-06.at.2.11.16.PM.mov

I'm not able to replicate this issue in local though I see it in PR preview link. Can you pull the latest code and test it again in local?

I am still seeing it locally after pulling the latest code:

Screen.Recording.2025-11-20.at.10.03.55.AM.mov

I'm using the the latest version of Chrome

[pmakode-akamai]

I'm still seeing the issue (especially when the window's vertical size is reduced).

I think the issue might be caused by the fixed height of the dropdown. This may need to be adjusted based on the viewport height (vh/%)

on Prod (working)	on this branch (preview link)	on this branch (local)

[pmakode-akamai]

I didn't notice any layout issues now across different viewports on the preview link, locally or with MSW enabled. Thanks for fixing this 👍. The updated pnpm-lock.yaml look good as well

[grevanak-akamai]

When I first load the page and try to select a time, there's a pretty odd UI bug I'm observing on this branch that doesn't happen in prod:
Screen.Recording.2025-11-06.at.2.11.16.PM.mov

I'm not able to replicate this issue in local though I see it in PR preview link. Can you pull the latest code and test it again in local?

I am still seeing it locally after pulling the latest code:

Screen.Recording.2025-11-20.at.10.03.55.AM.mov
I'm using the the latest version of Chrome

@dwiley-akamai please retest now

[jaalah-akamai]

Thanks for the changes - looks good 👍

[dwiley-akamai]

The issue I mentioned previously appears to be resolved 👍🏾

[smans-akamai]

Tested out a few scenarios and didn't see any issues. It looks like the previous navigation issue had also been resolved, so this looks good to me!