
Why Terraform Breaks After Day-1 And How Terraform Actions Fix It
Let me start with something most infrastructure engineers might not say out loud — Terraform solves Day-1 beautifully and then kinda leaves you hanging. You write your HCL, run terraform apply , and everything is provisioned perfectly. The state file appears impeccable. But six months later that same infrastructure has been poked, patched, manually changed and silently drifted away from what terraform thinks exists. No one realizes this until something breaks in production. This article is about that “gap” between provisioning and actually managing infrastructure across its entire lifetime. Day-2 Is Where Infrastructure Goes to Die (Slowly) When a full stack is provisioned onto AWS using Terraform it has a good state and everything is the same, and then after some time passes and a deployment fails, someone logs into the console and changes a security group rule; now the deployment has been successful… but this change has not been documented and no tickets have been raised regarding th
Continue reading on Dev.to
Opens in a new tab




