A lot of these tools are created in an atmosphere of corporate redundancy. Sure your test framework, regional deplyments, A/B testing, CI, code coverage, storage infra, network infra, security settings, and app configurations are held in a 20000-line yaml-within-yaml-within-yaml disaster.
On the other hand, at least they aren’t hand-coded by Steve (who left the company last week)
A higher bus factor is nice, but there's almost certainly more thought and wisdom in a popular CI/CD setup than Steve's scripts.
Came here with that exact quote in my clipboard. I have a medical background prior to software, and one of the key learnings there is that wherever there is scope for a human to make a mistake, that mistake will (eventually) be made. It's therefore crucial that wherever possible the capability of making that mistake is eliminated. I see automated deployment as falling into a similar category of utility.
> The obvious answer is because it is easier.
No. The answer is that it’s more robust in the face of operator error, it’s repeatable and it’s auditable.