Module 25 · Chapter 22: Runbooks and checklists
Runbooks and checklists
In short
A good runbook can be run by someone else without asking: every step has a command, an expected result, a way to check, and what to do if it fails. Green means the script finished; evidence means the change is really live.
After this lesson you can
- Write a release runbook someone else can run
- Put together before and after release checklists
- Check every step with evidence, not with a green status
Sign in to read this lesson
The title and summary are open to everyone. The full lesson is for signed-in learners.