> Perhaps what is required is a completely different attitude to config changes, which treats them as testable, applies them incrementally and allows simple rol

> Perhaps what is required is a completely different attitude to config changes, which treats them as testable, applies them incrementally and allows simple rollback. > Code is stored in version control and extensively tested before deployment. Are config changes treated the same way? It certainly doesn't seem like it. Config changes should not be hard to test, hard to diagnose, and hard to rollback. Google already do this. The SRE book goes in to details https://landing.google.com/sre/books/ https://landing.google.com/sre/books/