Closed mouyigang closed 5 years ago
You are right, we should be making this easier.
We should make it possible to configure the retention policy at the L2 level, and probably default it to true
(to satisfy most use cases).
Aha, my mistake. We already have this property.
If you create your bucket like this:
new s3.Bucket(this, 'Bucket', {
/// ...
removalPolicy: cdk.RemovalPolicy.Orphan
});
Stack deletion will not complain.
We've made the orphaning behavior default. For new stacks, you will not experience this behavior anymore.
My demo app builds codebuild and codepipeline, after two commits to codecommit and successfully build, I decided to destroy everything:
But s3 bucket was not deleted:
Expect: Either state that cdk destroy doesn't destroy s3 buckets, or successfully delete s3 bucket.