-
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
fix(core): RemovalPolicy.SNAPSHOT can be added to resources that do not support it #20668
Conversation
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.
Let's add a warning for this that isn't under a feature flag so that customers who don't opt in to the feature flag will still get alerted, but not have an error thrown.
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…ot support it (aws#20668) fixes aws#20653, which was reported for opensearch domains, but also fixes this issue for all other resources that allowed this removal policy but did not actually support it. previously, the behavior was a successful synth and deploy, and cloudformation ignores the snapshot removal policy if it is not supported by the resource. because of this, i believe that i have to add this fix behind a feature flag to avoid breaking customers. without the feature flag, the best we can do is add a warning to the stack notifying customers that the snapshot policy is useless. ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
fixes #20653, which was reported for opensearch domains, but also fixes this issue for all other resources that allowed this removal policy but did not actually support it.
previously, the behavior was a successful synth and deploy, and cloudformation ignores the snapshot removal policy if it is not supported by the resource. because of this, i believe that i have to add this fix behind a feature flag to avoid breaking customers.
without the feature flag, the best we can do is add a warning to the stack notifying customers that the snapshot policy is useless.
All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integ
to deploy the infrastructure and generate the snapshot (i.e.yarn integ
without--dry-run
)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license