You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: