Five Features I Shipped in tfdrift That Changed How We Handle Terraform Drift

<p>Terraform state describes what you <em>think</em> is deployed. Drift is the gap between that and reality: someone changes a security group in the console during an incident, an

<h2> When Terraform Gets Slow </h2> <p>Our Terraform state file grew to 500+ resources. Plans took 8 minutes. Applies timed out. State locking conflicts were daily. Something had

<p>I Built an AI That Fixes Terraform Drift Automatically</p> <p>If you've worked with Terraform long enough, you know the feeling. You run terraform plan and suddenly there are

<p>My Terraform drift pipeline could detect a manual EC2 tag change, classify it as LOW, and run Terraform to remove it.</p> <p>Then the pipeline moved on.</p> <p>The evidence

<p>Anthropic shipped Opus 4.7 on April 16, 2026. Same $5/$25 pricing as 4.6. Same 1M context. Same 128K output ceiling. Different model entirely when you put it in an agentic

<p>You know the ritual.<br /> </p> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>terragrunt run <span class="nt">--all</span> <span

<p><strong>Introduction</strong></p> <p>A <strong>two-tier architecture</strong> on AWS — the bread and butter of real-world cloud deployments. Here's the idea:</p> <ul> <li>

<p>I opened the AWS console, selected an EC2 instance, added a tag, and saved it.</p> <p>The tag did not exist in Terraform. The deployed infrastructure now said one thing while