The seqerakit integration allows one to provision a brand new AWS Batch CE (via TowerForge) as part of the terraform apply process. 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 a terraform destroy action prior to cleaning up resources inside Tower (due to Tower controlling the state of these objects rather than TF).

The make destroy command should be enhanced to loop through all TowerForge-generated CEs in the implementation, and destroy them, prior to invoking the terraform destroy command.