Terraform

Terraform configurations declare resources and relationships, while providers translate operations into the APIs of cloud platforms or other systems. State maps declared objects to real resources and retains information needed for planning. The plan compares configuration and tracked infrastructure to propose actions; apply performs them. Modules reuse a set of definitions without eliminating the need to understand their inputs and outputs. Terraform is a particular tool, distinct from Infrastructure as Code as a broader practice. A resource name or parameter change can affect identity, replacement and downstream dependencies.

The practitioner chooses providers and versions, organizes modules around clear ownership and keeps environment values separate from reusable definitions. They protect shared state, coordinate concurrent work and inspect plans for replacement or deletion before applying. They import or migrate existing resources carefully and detect drift from manual changes. Useful work yields a reviewed configuration and known infrastructure state, with verification of the actual deployed resources and a migration strategy for persistent data or interfaces that cannot be replaced casually.

A valid plan can still implement the wrong design, and applying a saved plan after the environment changes needs careful workflow controls. State and plans can reveal secrets; conflicts or damaged state can complicate management. Provider behavior determines which changes require replacement. Check action lists, resource ownership and state protection. Terraform does not guarantee a reversible deployment or automatically validate the application that runs on the infrastructure.