Config Management Camp 2024 Ghent

In a small environment a single devops engineer or team of engineers can automate changes to production with a well tuned configuration management system. In a large production environment that spans the globe and contains more functional parts than a single team could manage, running config management as continuous delivery is practically untenable. Risky changes need to be incremented by smaller deployment steps or separated into smaller deliverables. High risk services and locations need more validation time before accepting changes. With many teams pushing dozens of changes to production daily, there is a need for health-mediated deployment. Ideally, service owners self-serve change management+health metrics with state enforcement completely decoupled and below the API.