-
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: report undeleted resources after cdk destroy #21806
Comments
We also really need this in the console. Great idea! |
Thanks for opening a new issue for visibility The approach you've described to fetch stack resources seems feasible for us to implement without too much overhead We accept contributions! Check out our contributing guide if you're interested - there's a low chance the team will be able to address this soon but we'd be happy to review a PR 🙂 |
Do you have any tips for where to look in the code to start hacking away at a solution here? Haven't contributed to this repo yet much. Once we build something into the cli for it, how do we go about getting it in the UI of the console? (amazonian here) |
We don't have any control over the console UI, since the CDK isn't its own service and relies on CloudFormation This file is where our entrypoint and CLI options are 🙂 |
@niebloomj As the issue has been quiet for some time, I hope you don't mind if I give this one a shot :) |
Thank you very much for the PR @TrygviZL! We'll try to give it a review soon 🙂 |
Don't mind at all. Very much appreciated! Excited to learn from your PR |
Describe the feature
Hi,
It would be nice if the CDK cli could report resources that will not be deleted by
cdk destroy
.Ideally, this report is displayed before confirmation.
Note: This is a duplicate of #15749 which was closed automatically.
See this comment for possible workarounds.
Use Case
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.38.1
Environment details (OS name and version, etc.)
any OS
The text was updated successfully, but these errors were encountered: