This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Incomplete cleanup / Cost trap #276
Labels
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
good first issue
Related to contributions. See CONTRIBUTING.md
in-progress
Issue is being actively worked on.
p1
The workshop and CDK itself lack information about how to clean up correctly and which cost may occur.
As stated in #126 and ignored for years in aws/aws-cdk#986, the user is left with a DynamoDB table, S3 bucket, CloudWatch logs and CloudFormation stack after finishing the workshop, without knowing about their existence.
This is a dark pattern (some may call it worse) as the user acts in good faith and in compliance with the cleanup section, yet will be left in an unclean state for redeployment and could be charged for resources he thought were destroyed.
I suggest the following steps:
RemovalPolicy
optionscdk bootstrap --destroy
commandThe text was updated successfully, but these errors were encountered: