Change Management¶
How changes reach production at SnowOps and how we keep the change-management evidence (SOC2 CC8.1 / ISO A.12.1.2). The normal path is CAB pre-approval; the exception is the emergency / break-glass path, recorded and reviewed after the fact.
Contents¶
| Page | Use it for |
|---|---|
| Emergency Change (break-glass) | A change that can't wait for CAB pre-approval — the emergency-change label, the inline Emergency Change Record, and the mandatory retrospective review. |
The two paths¶
- Normal change — the PR is assessed by R4 (
apps/cab-automation/); if it requires CAB it is reviewed and approved before merge. R1 (pr-template-check.yml) enforces the standard PR template; R2 (apps/change-log/) records what shipped. - Emergency change (R3) — when waiting for CAB would cause unacceptable harm
(a live P1, a security containment action), the
emergency-changelabel bypasses pre-approval. In exchange the change must carry a complete inline Emergency Change Record and a committed retrospective CAB review within the SLA. See emergency-change.md.
See also: the manual test runbooks (R1–R4 sign-off) and
docs/context/00-asset-glossary.md for
code → name lookups.