[DRAFT — AWAITING APPROVAL]
Terraform vs Manual Infrastructure
Why click-ops becomes a liability, and how to bring existing infrastructure under code.
Manually created infrastructure — click-ops — works until someone needs to reproduce it, audit it or change it safely. Infrastructure as code (IaC) with a tool such as Terraform or OpenTofu addresses all three.
The risks of manual infrastructure
- Environments drift apart and no one knows exactly why
- Changes have no review or history
- Recovery after a failure depends on memory
- Knowledge concentrates in a few people
What IaC provides
Infrastructure is defined in version-controlled files, changes are reviewed as plans before they apply, and the same modules can build consistent environments.
Bringing existing infrastructure under code
- Inventory what exists and decide what to manage
- Import resources into state incrementally, starting with the most change-prone
- Introduce reusable modules for common patterns
- Run plans in CI and apply through a controlled pipeline
- Detect drift regularly
Keep state safe
Use remote state with locking, restrict who can apply, and never store secrets in plain text in configuration or state where avoidable.