<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Terraform on takebakker.dev</title><link>https://takebakker.nl/tags/terraform/</link><description>Recent content in Terraform on takebakker.dev</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Take Bakker</copyright><lastBuildDate>Sun, 11 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://takebakker.nl/tags/terraform/index.xml" rel="self" type="application/rss+xml"/><item><title>Reference: Opinion/Experience Post</title><link>https://takebakker.nl/drafts/reference-opinion-post/</link><pubDate>Sun, 11 Oct 2026 00:00:00 +0000</pubDate><guid>https://takebakker.nl/drafts/reference-opinion-post/</guid><description>&lt;p&gt;Terraform state drift is treated as an edge case. In my experience it&amp;rsquo;s more like a regular occurrence that teams aren&amp;rsquo;t&#10;monitoring for.&lt;/p&gt;&#10;&lt;p&gt;The scenario is always some variation of: someone makes a manual change in the portal — usually under time pressure,&#10;usually with good intentions — and doesn&amp;rsquo;t update the Terraform code to match. The state file now reflects reality as&#10;Terraform last knew it, not reality as it actually is. Next &lt;code&gt;terraform plan&lt;/code&gt; shows unexpected changes. The team gets&#10;confused, makes it worse, or both.&lt;/p&gt;</description></item></channel></rss>