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 secondary instance #16398

Conversation

modular-magician
Copy link
Collaborator

To Create a Secondary Instance inside a secondary cluster, set the instance_type to point to the cluster_type of the associated secondary cluster & set lifecycle.ignore_changes = [instance_type]
Avoid setting instance_type = "SECONDARY", as promoting a secondary cluster to a primary cluster also modifies the instance_type of the associated secondary instance

  instance_type = google_alloydb_cluster.<secondary_cluster_name>.cluster_type
  lifecycle {
    ignore_changes = [instance_type]
  }

Release Note Template for Downstream PRs (will be copied)

alloydb: added "SECONDARY" as an additional option for `instance_type` field in `google_alloydb_instance` to support creation of secondary instance inside a secondary cluster. 
alloydb: added "deletion_policy" to `google_alloydb_cluster` to allow force-destroying instances along with their cluster. This is necessary to delete secondary instances, which cannot be deleted otherwise.
alloydb: increased default timeout on `google_alloydb_instance` to 120m from 40m

Derived from GoogleCloudPlatform/magic-modules#9203

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

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

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 Nov 27, 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