-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
(cli): introduce a new flag for CloudFormation's FORCE_DELETE_STACK
#30344
Comments
It would be very nice to have CDK leverage this feature. Although, I'm not entirely sure if recycling cdk destroy --mode FORCE_DELETE_STACK Which would allow for other modes, if the CF team adds any in the future. |
I don't think we should update |
cdk destroy --force
should use CloudFormation's FORCE_DELETE_STACK
FORCE_DELETE_STACK
I agree that it could be problematic to change the behaviour of an existing flag, so I updated the PR. |
@garysassano , thanks for submitting this FR. I agree with @nmussy ,since we have CDK Destroy, this behavior might be unexpected. Would need core team's input here on the consideration. |
Definitely a new flag on |
Describe the feature
It would be nice if we could introduce a new flag in the CDK CLI to take advantage of the new DeletionMode parameter with
FORCE_DELETE_STACK
value to make sure that the CloudFormation stack gets destroyed at all costs, bypassing any possible error that may be encountered.Use Case
Make the experience of force destroying a stack less annoying.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.143.0
Environment details (OS name and version, etc.)
WSL2 Ubuntu 22.04.3 LTS
The text was updated successfully, but these errors were encountered: