Terraform destroy without configuration files.
Occasionally, terraform destroy behaves like a stubborn donkey and doesn't want the way you want. What YOU WANT is
probably simply to destroy a Terraform configuration. What TERRAFORM WANTS is all the configuration files to exist,
be valid, dependencies in remote states be accessible, ... everything still be in perfect shape--yes, even if you don't want to
apply, but just destroy.
Terraform may have valid reasons to be so pedantic, but wouldn't it be convenient to have a way to bulldoze all resources managed by Terraform configuration no matter what, simply based on its state file? That's what Terradozer does for you.
Happy (terra)dozing!
TODO
- Terradozer first scans a given Terraform state file (read-only) to find all resources (excluding data sources),
then downloads the necessary Terraform Provider Plugins to call the destroy function of the providers' CRUD API via GRPC
(e.g., calling the Terraform AWS Provider to destroy a
aws_instanceresource)---this can be done without needing the configuration files. - Terradozer cannot infer the dependency graph from the state, as this information is stored in the configuration files. However, Terradozer retries smartly until all resources are destroyed.
- Terradozer shows all resources first and asks to confirm with
yesbefore proceeding wit a destroy (same as Terraform does) - Terradozer has a force mode to use Terradozer in an automated way, for example, in your CI pipeline
It's recommended to install a specific version of terradozer available on the releases page.
Here is the recommended way to install terradozer v0.1.0:
# install it into ./bin/
curl -sSfL https://raw.githubusercontent.com/jckuester/terradozer/master/install.sh | sh -s v0.1.0To delete all resources in a Terraform state file:
AWS_PROFILE=<myaccount> AWS_DEFAULT_REGION=<myregion> terradozer -state <path/to/terraform.tfstate>
Note that you need to provide credentials for the AWS account you want to destroy resources in via environment variables. The region is needed too, as the region information is not stored in the state. Having multiple regions in a state file is not yet supported.
To only see what would be deleted, add the dry run flag above -dry.
*By making use of Terraform's Provider Plugin Architecture, Terradozer would be able destroy any resource in a Terraform state file. However, the Terraform Provider configuration is not stored in the state and therefore I still need to investigate a way to generically provide a default configuration for any provider. Until now, Terraform AWS provide is the only supported provider, for which I statically added a default config. If you need any other provider, let me know, and I will help supporting it.
- Terradozer cannot know the region (as it is part of the Terraform configuration) in which your resources live. So, you need
to provide the region via
AWS_DEFAULT_REGION=<myregion>when running Terradozer.
This section is only relevant if you want to contribute to Terradozer and therefore run the tests. Terradozer has acceptance tests, integration tests checking against changes of behaviour in the Terraform Provider API, and of course unit tests.
Run unit tests
make test
Run acceptance and integration tests
AWS_PROFILE=<myaccount> AWS_DEFAULT_REGION=<myregion> make test-all