<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Frida Hansen</title>
    <description>The latest articles on DEV Community by Frida Hansen (@frida_hansen).</description>
    <link>https://dev.to/frida_hansen</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4215084%2Ffc1c9fce-5e2e-440b-857f-d2b65cab79e5.jpg</url>
      <title>DEV Community: Frida Hansen</title>
      <link>https://dev.to/frida_hansen</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/frida_hansen"/>
    <language>en</language>
    <item>
      <title>Terraform state is the real production database</title>
      <dc:creator>Frida Hansen</dc:creator>
      <pubDate>Sun, 01 Nov 2026 15:08:28 +0000</pubDate>
      <link>https://dev.to/frida_hansen/terraform-state-is-the-real-production-database-2d68</link>
      <guid>https://dev.to/frida_hansen/terraform-state-is-the-real-production-database-2d68</guid>
      <description>&lt;p&gt;A friend describes Terraform state as the database nobody backs up. I think about that every time I see a local state file in a repo.&lt;/p&gt;

&lt;p&gt;The baseline I now refuse to work without:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Remote state with locking.&lt;/strong&gt; S3 + DynamoDB is boring and correct.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One state per environment&lt;/strong&gt;, never a shared state with workspaces pretending.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An import path&lt;/strong&gt; that doesn't require editing state by hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drift detection on a schedule&lt;/strong&gt;, not when someone notices.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The failure I've seen twice: someone imports a resource into the wrong state, and the next apply tries to recreate production. Locking doesn't help if the lock is on the wrong file.&lt;/p&gt;

&lt;p&gt;The other thing: state contains secrets in plaintext. If the bucket isn't encrypted and access-controlled, you have a leak.&lt;/p&gt;

&lt;p&gt;It's not glamorous, but the state is the system. Treat it like a database: back it up, lock it, review changes to it.&lt;/p&gt;

&lt;p&gt;What's your drift detection setup?&lt;/p&gt;

</description>
      <category>terraform</category>
      <category>devops</category>
      <category>aws</category>
    </item>
    <item>
      <title>What I actually look for in a Terraform plan</title>
      <dc:creator>Frida Hansen</dc:creator>
      <pubDate>Thu, 29 Oct 2026 11:00:36 +0000</pubDate>
      <link>https://dev.to/frida_hansen/what-i-actually-look-for-in-a-terraform-plan-546i</link>
      <guid>https://dev.to/frida_hansen/what-i-actually-look-for-in-a-terraform-plan-546i</guid>
      <description>&lt;p&gt;I review plans for a living now, and I've stopped reading them top to bottom. The order I use:&lt;/p&gt;

&lt;p&gt;Replacements first. Anything with -/+ is a resource being destroyed and recreated. Often fine, occasionally a database. I look at that list before anything else.&lt;/p&gt;

&lt;p&gt;Then security group and IAM diffs, character by character. A single 0.0.0.0/0 or a widened action list is easy to miss in a wall of text and hard to undo quietly.&lt;/p&gt;

&lt;p&gt;Then anything with a count or a for_each that grew. Three new replicas is a cost question, three hundred is an incident waiting to happen.&lt;/p&gt;

&lt;p&gt;Finally deletions. A destroy on something that still has data is the only change I'll stop a deploy for.&lt;/p&gt;

&lt;p&gt;The one rule I'd give anyone: if the plan is too long to review, that's the finding. Split the change. A two-hundred-line plan gets approved by scrolling, and scrolled-over plans are how prod gets interesting.&lt;/p&gt;

&lt;p&gt;Nothing here is clever. It's just a reading order that stops me from approving what I didn't see.&lt;/p&gt;

</description>
      <category>terraform</category>
      <category>devops</category>
      <category>aws</category>
    </item>
  </channel>
</rss>
