<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Versioning on Cloud Engineering Chronicles with Mohammad</title>
    <link>https://varmazyar.de/tags/versioning/</link>
    <description>Recent content in Versioning on Cloud Engineering Chronicles with Mohammad</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 05 Sep 2024 16:20:00 +0200</lastBuildDate>
    <atom:link href="https://varmazyar.de/tags/versioning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Effortless Terraform Management: How Terragrunt Keeps Your Code DRY and Efficient</title>
      <link>https://varmazyar.de/posts/terragrunt-how-to-keep-your-terraform-code-dry-and-maintainable/</link>
      <pubDate>Thu, 05 Sep 2024 16:20:00 +0200</pubDate>
      <guid>https://varmazyar.de/posts/terragrunt-how-to-keep-your-terraform-code-dry-and-maintainable/</guid>
      <description>Effortless Terraform Management: How Terragrunt Keeps Your Code DRY and Efficient Link to heading In 2016, an open-source tool called Terragrunt was released to address two key issues with Terraform: (1) the lack of state locking and (2) the inability to configure Terraform state as code. While Terraform has since introduced solutions like backends to handle these problems, new challenges emerged as infrastructure grew more complex. The biggest issue? Keeping your Terraform code DRY (Don’t Repeat Yourself) and easy to maintain across environments.</description>
    </item>
  </channel>
</rss>
