Skip to content
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

Destroy old CDK log groups in sandbox environment #415

Open
jlkravitz opened this issue Dec 19, 2024 · 0 comments
Open

Destroy old CDK log groups in sandbox environment #415

jlkravitz opened this issue Dec 19, 2024 · 0 comments
Assignees

Comments

@jlkravitz
Copy link
Collaborator

When I deploy my sandbox, it creates several log groups. When I run cdk destroy "Sandbox/*", then deploy again, I would expect a clean deploy without extraneous resources in my AWS environment. I know several resources are hard to remove completely due to race conditions and other AWS quirks.

That said, it seems like log groups on AWS CloudWatch are not deleted. I've found it difficult to sift through logs when testing because there are often many log groups with similar names. I have to click through all of them to find the 'active' group.

I may be doing something wrong on the AWS side of things, so if that's the solution to this problem, that works, too! But if there's a relatively easy way to delete the log groups when destroying the AWS environment, that'd probably be helpful regardless.

@jlkravitz jlkravitz changed the title Destroy old CDK log groups Destroy old CDK log groups in sandbox environment Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants