<?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 Yaklab</title><link>https://www.yaklab.org/tags/configuration-management/</link><description>Recent content in Configuration-Management on Yaklab</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 James Ainslie</copyright><lastBuildDate>Wed, 08 Apr 2026 07:28:42 -0400</lastBuildDate><atom:link href="https://www.yaklab.org/tags/configuration-management/index.xml" rel="self" type="application/rss+xml"/><item><title>The Desired State of Things</title><link>https://www.yaklab.org/posts/desired-state-of-things/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.yaklab.org/posts/desired-state-of-things/</guid><description>&lt;p&gt;It&amp;rsquo;s 2am. Something is broken in production. An engineer SSHes into the box, finds the problem (a config file with the wrong value), fixes it, restarts the service, watches the metrics recover. Crisis averted. Everyone goes back to sleep.&lt;/p&gt;
&lt;p&gt;The Ansible playbook never learns about the fix. The next scheduled run either overwrites it or, more likely, doesn&amp;rsquo;t run at all because nobody wants to roll the dice on a Friday. Six months later, someone re-provisions the server from the same playbook and the old bug is back. Nobody connects the dots for another two weeks.&lt;/p&gt;</description></item></channel></rss>