-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(rds): default DatabaseCluser and DatabaseInstance storageEncrypted
to true
(under feature flag)
#32695
base: main
Are you sure you want to change the base?
feat(rds): default DatabaseCluser and DatabaseInstance storageEncrypted
to true
(under feature flag)
#32695
Changes from 24 commits
d80befc
ff3521d
319e467
83d402d
9ce2d46
221b872
75192b0
04fe2b2
d1c6c06
576289e
6bd263d
da306c0
6077185
4497f62
c089ab2
dbea499
4af1515
3c317b0
26a9325
82f8e77
9130e4e
1086ef1
a327f10
becf0a7
14795d0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change affected a lot of integration tests. I opted to use the legacy behaviors for these tests because re-running the creation of all these databases would be extremely slow and expensive.
If someone at AWS with a "free"/"expensed" account would like to rerun all these failing tests, we could go that route, too.
I added explicit new tests for this behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think manually adding
"StorageEncrypted": true
to the templates would make those tests pass without the need to deploy the related resources (we expect the flag to work given that you added the new test).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the past, I've received PR feedback that you should never manually update snapshot files. I just confirmed that I could add this property manually to the snapshots and that would be an alternative solution to updating the stack definitions.
I'd like a +1 from an approver that this would be OK before I spend the time doing it, based on previous feedback that snapshots should never be manually edited.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Sounds good!
About the
isStorageLegacyUnencrypted
comment.Thanks for clarifying, I'm not sure why CFN defaults to unencrypted clusters and instances.
However, I left some comments on the implementation for small adjustments.