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

With ec2 setup add a mechanism to clean up all created resources in the account. #179

Open
jwmatthews opened this issue Nov 8, 2017 · 0 comments

Comments

@jwmatthews
Copy link
Member

@thoraxe raised the issue that catasb is not cleaning up after itself with ec2 provisioning.

There is no mechanism to clean up the various resources beyond the instance/volume that are provisioned.
Example: VPC, Security Groups, Subnets, etc.

This issue is tracking an ability to provide a "nuke_all.sh" or equivalent that a user can run to cleanup any resources created by catasb.

One thought for implementation is we could tag all resources with a "catasb" identifier then query the account for all resources matching the explicit tag and remove those for a nuke operation.

There is a concern of not making this part of typical workflow in a shared IAM account, as in a shared account it's expected that multiple users will be reusing the same VPC, Subnets, etc. In the shared use case we expect catasb to create a specific VPC once and for all users to reuse it. We wouldn't want individual users to "nuke" these shared resources after their testing is complete as it would adversely impact others in the account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant