Cloud Infrastructure · Cluster
Infrastructure as Code
Declarative provisioning and drift.
- 01 Desired State, Observed State, and the Reconciliation Loop Why declarative provisioning converges instead of executing steps, what a provider must implement to make convergence possible, and where the model stops describing reality.
- 02 Resource Graphs and Dependency Ordering How references between resources become directed edges, why a cycle is rejected before anything is created, and how ordering decisions change apply time and blast radius.
- 03 State as a Mapping Between Addresses and Real Objects What a provisioning state file actually stores, why it is the tool's only durable record of identity, and how concurrent access corrupts that record.
- 04 Count, for_each, and the Stability of Instance Addresses How a resource with a repetition argument becomes several state addresses, why index keys renumber on deletion while map keys do not, and what that costs at apply time.
- 05 What a Plan File Records and Why Applying It Is Not a Re-Plan How the plan is computed, what it stores beyond the proposed changes, and why the saved artifact can disagree with the world it is applied to.
- 06 Detecting Drift Without Recreating the World How a refresh distinguishes remote change from remote absence, why some differences cannot be seen at all, and what remediation does to the objects that were changed outside the tool.
- 07 Importing Existing Resources into a Declarative Configuration What adoption actually writes into state, why a written resource block must match the object before the plan is clean, and where import cannot reach.
- 08 Module Interfaces and the Cost of Hiding Structure Why a module boundary turns a graph into a black box, which abstractions leak through the interface, and how validation and outputs shape what callers can express.
- 09 Provider Versions, Schema Changes, and State Migration How a provider upgrade can change the meaning of stored state, why schema versions exist per resource type, and what an upgrade path can and cannot fix.
- 10 Designing for Blast Radius in a Single Apply How state boundaries, replacement rules, and apply ordering determine how much infrastructure a failed run can take down, and what can be enforced before the call is made.