[ Enhancement ] Add mechanism to tear down TowerForge-generated environments prior to terraform destroy
#108
Assignees
Comments
|
@schaluva - this could be a good ticket for you to run with: solves a genuine problem, the project already has most of the infrastructure necessary to implement this extension, and it gives you a chance to play with the Tower APIs. Depending how your testing goes today, we can align this afternoon / early next week. |
gwright99
changed the title
terraform destroyterraform destroy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The seqerakit integration allows one to provision a brand new AWS Batch CE (via TowerForge) as part of the
terraform applyprocess. While this is very handy from a stand-up process, it can result in orphan resources in the AWS Account in the event that a user invokes aterraform destroyaction prior to cleaning up resources inside Tower (due to Tower controlling the state of these objects rather than TF).The
make destroycommand should be enhanced to loop through all TowerForge-generated CEs in the implementation, and destroy them, prior to invoking theterraform destroycommand.The text was updated successfully, but these errors were encountered: