Configure non-production database clusters to match production cluster. #46560
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cat5inthecradle
approved these changes
May 27, 2022
|
✅ confirming that these updates require no interruption |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are a few configuration settings on the staging/test/levelbuilder/adhoc Aurora database clusters that are properties of the cluster Resource and not configured via ParameterGroups (see #45907 ). Update them to match what has been manually configured on the production cluster.
Links
Testing story
Deployment strategy
None of the Properties being modified on this Resource trigger Replacement or Interruption of the cluster:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html
Follow-up work
Privacy
Security
Caching
PR Checklist: