<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infrastructure as Code on Saurabh Chaubey</title>
    <link>https://saurabh-chaubey.com/tags/infrastructure-as-code/</link>
    <description>Recent content in Infrastructure as Code on Saurabh Chaubey</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 20 Mar 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://saurabh-chaubey.com/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Terraform Modules as Contracts: Designing Interfaces That Work Across Any Environment</title>
      <link>https://saurabh-chaubey.com/post/devops/terraform-modules-as-contracts-designing-interfaces/</link>
      <pubDate>Fri, 20 Mar 2026 10:00:00 +0000</pubDate>
      
      <guid>https://saurabh-chaubey.com/post/devops/terraform-modules-as-contracts-designing-interfaces/</guid>
      <description>Stop designing modules around cloud APIs. Start designing them around what your team actually needs to say.
Here&amp;rsquo;s a question: when you add a new environment to your Terraform project, how much code do you touch?
If the answer involves editing module internals, adding if statements, or copying resource blocks — your module boundaries are in the wrong place. A well-designed Terraform module should work like a contract. The consumer says what they want.</description>
    </item>
    
    <item>
      <title>Terraform State Management for Multi-Environment Teams: Patterns That Actually Scale</title>
      <link>https://saurabh-chaubey.com/post/devops/terraform-state-management-multi-environment-teams/</link>
      <pubDate>Sun, 15 Mar 2026 10:00:00 +0000</pubDate>
      
      <guid>https://saurabh-chaubey.com/post/devops/terraform-state-management-multi-environment-teams/</guid>
      <description>Your state file is the single most dangerous file in your infrastructure. Here&amp;rsquo;s how to stop it from ruining your week.
One terraform destroy in the wrong terminal tab.
That&amp;rsquo;s all it takes to wipe out a production database, a Kubernetes cluster, or an entire network stack. Not because someone was careless — because the state management pattern made it easy to be in the wrong environment without realising it.</description>
    </item>
    
  </channel>
</rss>
