Your Automation Pipeline Is Not a Source of Truth
A CI/CD pipeline that runs without errors creates a sense of correctness. The job is green. The deployment happened. The infrastructure must reflect what it should. This logic feels sound, and it breaks down in a specific way worth understanding.
The pipeline knows what it was told to do at the time it ran. It does not know whether that was the right thing to do. And it cannot tell you whether the state it produced is still aligned with what the organization actually needs, because it has no persistent model of intended state to check against. It ran, it applied, it exited.
When a pipeline becomes the de facto source of truth, the actual authority over infrastructure state is distributed across pipeline history, environment variables, conditionals, and whatever was in the repository at the time of the last run. That is a fragile place to store operational intent.
What...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
