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: enable admin username and support cluster instance for aurora mysql #2079

Merged
merged 5 commits into from
Sep 4, 2024

Conversation

servicesenablement
Copy link
Contributor

Checklist:

  • Have you added Release Notes in the docs repositories?
  • Have you ran make run-integration-tests and make run-terraform-tests?
  • Have you ran acceptance tests for the service under change?
  • Have you followed the Conventional Commits specification?

…cluster

This is required to be able to import legacy instances from the legacy broker. Having to change the master password would result in instance recreation.

[TPCF-26822](https://jira.eng.vmware.com/browse/TPCF-26822)
Legacy broker creates only one cluster with one cluster instance and names the cluster instance the same as the cluster name itself. Any attempt to set the cluster instance identifier to something else would trigger an instance recreation which we do not want.
Copy link
Contributor

@zucchinidev zucchinidev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @FelisiaM, I think it looks good to me. I had doubts about the prohibit_update associated with the legacy_instance property, but I think I’m overengineering

@zucchinidev zucchinidev merged commit 8964c19 into main Sep 4, 2024
8 checks passed
@zucchinidev zucchinidev deleted the feat_enable_admin_username_for_aurora_postgres branch September 4, 2024 14:53
@FelisiaM FelisiaM changed the title feat: enable admin username and support cluster instance for aurora postgres feat: enable admin username and support cluster instance for aurora mysql Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

3 participants