<?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 Ajay Dhungel</title>
    <link>/tags/terraform/</link>
    <description>Recent content in Terraform on Ajay Dhungel</description>
    <generator>Hugo 0.125.0</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/terraform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Structure My Terragrunt Setup</title>
      <link>/posts/terragrunt-structure/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/posts/terragrunt-structure/</guid>
      <description>Introduction I first learned this setup back in 2022 at Genese Solution in Kathmandu. We were working toward the AWS DevOps Competency, which meant managing infrastructure across multiple client workloads, each with their own environments, their own state, and their own quirks. My mentors there, Dipendra Dangal, Pawan Chaulagain, and Sunit Khadgi, had already figured out the hard way that plain Terraform at that scale was painful.&#xA;The specific problem was Terraform workspaces.</description>
    </item>
  </channel>
</rss>
