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

Alloydb CRR Promote Secondary Cluster #16413

Conversation

modular-magician
Copy link
Collaborator

To Promote a Secondary Cluster, perform the following 2 changes in the secondary cluster config.

  1. Modify cluster_type = "PRIMARY"
  2. Remove the entire secondary_config field from the config 

Before

resource "google_alloydb_cluster" "secondary" {
  <required-fields> = <value>
  <other-fields> = <value>

  cluster_type = "SECONDARY"
  secondary_config {
    primary_cluster_name = google_alloydb_cluster.primary.name
  }
}

After

resource "google_alloydb_cluster" "secondary" {
  <required-fields> = <value>
  <other-fields> = <value>

  cluster_type = "PRIMARY"
}

After promotion the secondary cluster becomes an independent primary cluster.

Release Note Template for Downstream PRs (will be copied)

alloydb: added support for promotion for `SECONDARY` `google_alloydb_cluster` resources

Derived from GoogleCloudPlatform/magic-modules#9271

Co-authored-by: Riley Karson <rileykarson@google.com>
Co-authored-by: Shubham Sahu <shubhsahu@google.com>
[upstream:e6651ccd68f469385bc0004067c93ca5f773848d]

Signed-off-by: Modular Magician <magic-modules@google.com>
@modular-magician modular-magician merged commit 2445abc into hashicorp:main Oct 31, 2023
2 checks passed
Copy link

github-actions bot commented Dec 1, 2023

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant