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 we create test environments they are only meant to be temporary. The build cleans up the environments automatically but when creating them locally or if there is a glitch in the pipeline it's possible that they wouldn't be cleaned up. If they are all tagged it would be easy to check if there are any temporary resources that should be removed manually.
This repo seemed like the most promising after a little investigation but it might be worth googling around once to see if anything else is around:
The text was updated successfully, but these errors were encountered:
ScottG489
changed the title
Tag temporary test resources accordingly so we can easily identify if any were not cleaned up
Tag temporary test resources in AWS accordingly so we can easily identify if any were not cleaned up
May 9, 2021
When we create test environments they are only meant to be temporary. The build cleans up the environments automatically but when creating them locally or if there is a glitch in the pipeline it's possible that they wouldn't be cleaned up. If they are all tagged it would be easy to check if there are any temporary resources that should be removed manually.
This repo seemed like the most promising after a little investigation but it might be worth googling around once to see if anything else is around:
https://github.com/jckuester/awsweeper
The text was updated successfully, but these errors were encountered: