2.4. Reflection Checkpoint

Key Takeaways

• Providers are plugins, downloaded during init, that translate Terraform's generic CRUD into platform API calls — which is why core stays platform-neutral.
• Declare providers and version constraints in required_providers; the .terraform.lock.hcl lock file records the exact versions chosen and should be committed for reproducibility.
• Use multiple provider configurations with alias to target several regions, accounts, or clouds from one configuration.
• State is the indispensable mapping between configuration and real resources; it stores metadata and cached attributes, can contain plaintext secrets, and is not safely disposable.

Connecting Forward

Phase 3 puts these mechanics into motion. You'll walk the day-to-day command cycle — init to set up, fmt and validate to keep configuration clean and correct, then plan, apply, and destroy to drive the reconciliation loop you learned in Phase 1. Watch how each command touches providers and state in predictable ways.

Self-Check Questions

• Explain why terraform init is required before most other commands, in terms of providers, the lock file, and the backend.
• A configuration uses ~> 4.2 for a provider. CI installs 4.9 but your laptop has 4.2. What single file would make these consistent, and what command updates it intentionally?
• Why is protecting the state file a security concern, not only an operational one?