Amazon RDS deployment strategy #341
Merged
+28
−2
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.
Background
This PR enables the dynamic setup of Amazon RDS deployment strategies. Previously, the only option was to deploy RDS instances using a Multi-AZ configuration, which, while providing high availability, is costly and can increase release test runtimes.
Some release tests may not require such a high level of availability and can work with the Single-AZ Configuration. Therefore, the ability to dynamically configure deployment strategies offers a more flexible and efficient approach.
This PR also allows for the dynamic setup of the
allow_major_version_upgrade
variable, further enhancing customization and optimization.Relates to
Postgres Compatibility release test = https://hashicorp.atlassian.net/browse/TF-16228
How Has This Been Tested
The changes do not introduce significant modifications. Care has been taken to ensure that existing release tests are not disrupted by running the following GHA run -:
made
ci-aws-fdo-docker-active-active-feature
and GHA runhttps://github.com/hashicorp/terraform-enterprise/actions/runs/12256134039/job/34190732349