Automation & Tools
·
15 min read
So, your runbook repo is now shared. Three of you commit to it, the playbooks get used in real change windows, and last Tuesday somebody pushed broken YAML straight to main without anyone noticing.
So, your runbook repo is now shared. Three of you commit to it, the playbooks get used in real change windows, and last Tuesday somebody pushed broken YAML straight to main without anyone noticing.
Somebody asks in standup: “why did we change the ACL on edge-fw-02 last quarter? Who did it, and what else did they touch?” You know the answer lives in the repo.
You’ve had git in your daily workflow for a few weeks. You’ve got the basics down, until you do one of these… You committed vault_password.txt and pushed it before your second coffee.
Last Tuesday you made changes to a playbook because the on-call engineer needed an ACL pushed in a hurry.