Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: [UIE-8269], [UIE-8290] - DBaaS: Access Controls text update, fix defaultDB for legacy instances #11376

Conversation

mpolotsk-akamai
Copy link
Contributor

Description 📝

DBaaS: Access Controls text update, fix defaultDB for legacy instances

Changes 🔄

  • Summary Tab: updated 'Database name' for legacy instances
  • Database Create > Access Controls: updated copy, placeholder, button text
  • Settings Tab > Manage Access: updated copy (only for new instances)
  • Manage Access Drawer: updated copy, placeholder, button text (only for new instances)

Target release date 🗓️

12/10/24

Preview 📷

Before After
Screenshot 2024-12-04 at 8 19 32 PM Screenshot 2024-12-04 at 8 19 48 PM
Screenshot 2024-12-04 at 8 20 33 PM Screenshot 2024-12-04 at 8 21 02 PM
Screenshot 2024-12-04 at 8 22 32 PM Screenshot 2024-12-04 at 8 22 45 PM
Screenshot 2024-12-04 at 8 24 44 PM Screenshot 2024-12-04 at 8 24 37 PM

How to test 🧪

Prerequisites

(How to setup test environment)

  • dbaasV2 feature flag set to GA

Verification steps

(How to verify changes)

  • Select the legacy database and navigate to the Summary tab. Verify that the Database Name value is updated.
  • Navigate to the Database Create > Access Controls. The copy text, placeholder, and button text are updated.
  • Navigate to the Settings tab and select Manage Access. The copy text is updated (applicable only for new instances).
  • On the Landing Page, click the Action Menu and choose Manage Access Controls. Verify that the Manage Access Drawer has updated copy text, placeholder, and button text (applicable only for new instances).
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 unit tests are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

@mpolotsk-akamai mpolotsk-akamai requested review from a team as code owners December 5, 2024 15:27
@mpolotsk-akamai mpolotsk-akamai requested review from jdamore-linode, dwiley-akamai and abailly-akamai and removed request for a team December 5, 2024 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant