-
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
RDS: Missing default Snapshot deletion policy #3298
Comments
Hi @nmussy, Thank you for commenting and bringing this to our attention. I did a quick search and validated, this is indeed a gap. We will look into this problem as soon as we are able. Thank you again, and please know that these contributions really help our project grow and improve. 😸 |
Thank you for CDK I'm loving it. |
I just stumbled across this issue too. Default CDK behaviour is to "Retain" clusters and instances when it should actually be "Snapshot" according to Cloudformation documentation. |
…ance to Snapshot The 'Snapshot' retention policy is a special one used only for RDS. It deletes the underlying resource, but before doing that, creates a snapshot of it, so that the data is not lost. Use the 'Snapshot' policy instead of 'Retain', for the DatabaseCluster and DbInstance resources. Fixes aws#3298 BREAKING CHANGE: the default retention policy for RDS Cluster and DbInstance is now 'Snapshot'
…ance to Snapshot The 'Snapshot' retention policy is a special one used only for RDS. It deletes the underlying resource, but before doing that, creates a snapshot of it, so that the data is not lost. Use the 'Snapshot' policy instead of 'Retain', for the DatabaseCluster and DbInstance resources. Fixes aws#3298 BREAKING CHANGE: the default retention policy for RDS Cluster and DbInstance is now 'Snapshot'
…ance to Snapshot The 'Snapshot' retention policy is a special one used only for RDS. It deletes the underlying resource, but before doing that, creates a snapshot of it, so that the data is not lost. Use the 'Snapshot' policy instead of 'Retain', for the DatabaseCluster and DbInstance resources. Fixes aws#3298 BREAKING CHANGE: the default retention policy for RDS Cluster and DbInstance is now 'Snapshot'
…ance to Snapshot (#8023) The 'Snapshot' retention policy is a special one used only for RDS. It deletes the underlying resource, but before doing that, creates a snapshot of it, so that the data is not lost. Use the 'Snapshot' policy instead of 'Retain', for the DatabaseCluster and DbInstance resources. Fixes #3298 BREAKING CHANGE: the default retention policy for RDS Cluster and DbInstance is now 'Snapshot'
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
What is the current behavior?
If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce
Both RDS Instance and Cluster classes use the
RemovalPolicy
enum for their removalPolicy property, which does not implement the defaultSnpashot
optionWhat is the expected behavior (or behavior of feature suggested)?
The Snapshot option should be available. Changing the default to
Snapshot
would also be preferable in my opinion.What is the motivation / use case for changing the behavior or adding this feature?
Fix gap, possibly gain consistence with CloudFormation's default value.
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
The
CfnDeletionPolicy
enum does implement the Snapshot option:aws-cdk/packages/@aws-cdk/core/lib/cfn-resource-policy.ts
Line 96 in 4a0272d
The text was updated successfully, but these errors were encountered: