Mark Alloydb instance database_flags as default_from_api #17128
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Marking the database_flags field in the alloydb instance resource to be default_from_api
This is needed to reflect the actual database_flags for secondary instance, as the database_flags are copied from primary instance to secondary instance during secondary instance creation.
If the database_flags is not set for secondary instance, it successfully copies the flags during the creation phase.
However, with any further
terraform apply
command, it believes that the database_flags needs to be removed as the config doesn't have the database_flags field and performs an update operation instead.Marking default_from_api for the field to true ensures that this doesn't happen
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#9868