-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
Nuke VPCs and related resources #57
Comments
I am interested in working on this and I created some files to delete the VPC itself, but of course if there are resources associated with the VPC, then you must delete them first or the VPC cannot be deleted. What would be the general approach for nuking the resources associated with the VPC? Should you first nuke all of the VPC related resources individually, and then nuke the VPC? |
Yup! Probably need to delete subnets, route tables, peering connections, and VPC endpoints first. |
FWIW, the code to delete VPCs is implemented now, although it can only be invoked through the |
I would like to see this implemented ASAP and I'm happy to help, would it be preferred to re-use the same code used for the default vps or would it be better to implement like the rest of the resources all individually and in the right order? |
Hi @ekristen - thanks for offering to help! You should be able to reuse the functionality of |
A nice to have (but not critical) for the future would be the ability to nuke VPCs and all related resources:
The text was updated successfully, but these errors were encountered: