<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>configuration-management on Platform Engineering and Authentication</title>
    <link>https://codepurrpurr.io/tags/configuration-management/</link>
    <description>Recent content in configuration-management on Platform Engineering and Authentication</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://codepurrpurr.io/tags/configuration-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Intent-Driven Ansible Through Metadata Contracts</title>
      <link>https://codepurrpurr.io/platform-engineering/intent-driven-ansible-design/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://codepurrpurr.io/platform-engineering/intent-driven-ansible-design/</guid>
      <description>Problem Ansible is procedural by design. That is not inherently a problem.
The problem starts when the playbook becomes responsible for deciding what kind of system it is building.
As application families grow, orchestration logic accumulates branches:
 environment-specific conditionals hostname checks package selection logic server-role branching application-specific execution paths  The playbook stops being an execution engine and becomes a decision engine.
It grows harder to reason about, harder to test, and harder to extend without introducing unintended behavior.</description>
    </item>
    
  </channel>
</rss>
