<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloud-Governance on Thibaut Tauveron</title>
    <link>https://blog.tauveron.com/tags/cloud-governance/</link>
    <description>Recent content in Cloud-Governance on Thibaut Tauveron</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 23 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.tauveron.com/tags/cloud-governance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Designing Terraform for promotion, not divergence</title>
      <link>https://blog.tauveron.com/designing-terraform-for-promotion-not-divergence/</link>
      <pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.tauveron.com/designing-terraform-for-promotion-not-divergence/</guid>
      <description>&lt;p&gt;Most Terraform problems are not really caused by Terraform itself. They appear when the operating model around infrastructure changes makes divergence easier than controlled promotion.&lt;/p&gt;&#xA;&lt;p&gt;I saw this in a regulated cloud environment where the Terraform setup had become harder to govern over time. Separate repositories, environment-specific branches, and fragmented workflows made it too easy for environments to drift apart.&lt;/p&gt;&#xA;&lt;p&gt;This was not just a maintainability issue. It made changes harder to track, promotion across environments less reliable, and left too much knowledge and control with the infrastructure team. As a result, self-service became harder to expand without weakening governance.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
