https://latini.dev/tags/configuration/Recent content in Configuration on F. Latini - IT EngineerHugoenThu, 12 Nov 2026 08:00:00 +0000https://latini.dev/posts/the-change-that-skipped-the-pipeline/Thu, 12 Nov 2026 08:00:00 +0000https://latini.dev/posts/the-change-that-skipped-the-pipeline/<p><strong>TL;DR</strong> - Most platform teams have spent years making code deploys safe: review, tests, a canary, a one-command rollback, a record of who shipped what. Then production changes in a dozen other ways that touch none of it - a feature flag flipped to everyone at once, a global config value edited in a web UI, a security group changed in the cloud console, a manual <code>UPDATE</code> in a database shell, a DNS record, an IAM policy, a vendor setting. In most organisations I have worked with, those side doors start a large share of the incidents, and the change failure rate cannot see any of them because it only counts deploys. The cure is not to force every change through a twenty-minute pipeline. It is to give every change channel the properties that made deploys safe - a record, a proportionate review, a staged rollout and a fast undo - and to make &ldquo;what changed in the last hour?&rdquo; a single query instead of a question in Slack.</p>