1.4. Reflection Checkpoint

Key Takeaways

• IaC's core value is turning infrastructure into a reviewable, versioned, repeatable artifact — automation is a means, not the point.
• Terraform is declarative and provisioning-focused: you describe the desired end state, and Terraform computes the create/update/destroy actions to reach it.
• The reconciliation loop (config vs. state vs. real infrastructure) is the master key — almost every Terraform behavior follows from it.
• State binds your configuration to real resources; providers translate operations into platform API calls. Together they make one workflow work everywhere.

Connecting Forward

Phase 2 zooms into two of the three reconciliation inputs you just met: providers (how Terraform reaches each platform, how you install and version them) and state (what it really contains and why it matters). You'll move from the conceptual model to the concrete mechanics that the workflow in Phase 3 depends on.

Self-Check Questions

• Explain to a skeptical teammate why declarative IaC enables drift detection but imperative scripts generally don't.
• Walk through what Terraform would plan if you removed one of five identical resource blocks from your configuration — and which of the three reconciliation inputs drives that decision.
• Why is it accurate to say "Terraform acts on differences, not on configurations"?