How cloudtechner/ct-terraformer-automation works
Project type and purpose
• This is a small automation tool (“open-source tool” style) that orchestrates Terraformer imports of cloud resources into Terraform code and then merges Terraform state files.
• Purpose: simplify “infrastructure as code” workflows by wrapping the Terraformer CLI and Terraform state-merge operations in scripts.
File structure
• Top level:
• README.md – usage guide
• requirements.txt – Python dependencies
• terraformer-variables-automation.py – main orchestration script (Python)
• tfstate-merge.sh – helper to merge Terraform state files (Bash)
• No frontend/backend split – it’s a CLI-only tool.
• External dependencies: Terraformer CLI, Terraform CLI, AWS API (via Terraformer).
Key insights from the README
• Users install Python deps, run the Python script to import resources, then run the shell script to merge .tfstate.
• Generated code lands under a “generated/<provider>/<resource>/” directory tree.
Essential details
• Clearly separate “import” vs “merge” workflows as two sub-flows.
• Where requirements.txt and environment setup occur (Python runtime).
• Dependency flow: Python → Terraformer → AWS → HCL + JSON → Bash → Terraform CLI → consolidated state.