Policy As [Versioned] Code
summary
Claims a practical pattern: store policies in Git, use semantic version tags (examples 1.00, 2.00, 2-1-1), attach release notes and signatures, ship tests and signed releases, let consumers treat policy as a dependency so Renovate/Dependabot auto-PRs upgrades and you can push 10 updates in a single day without surprise downtime. Demonstrations use terraform checked by chekhov and Kubernetes checked by caverno, local and CI checks, and a simple bash driver to evaluate declared policy versions before deploy.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:33Chris Nesbitt Smith
- 6:59Where Do I See Policy as Code Going Wrong
- 16:08Version 2
- 31:57What's the Success Criteria
related talks
23mPolicy as [versioned] Code
25mPolicy as [versioned] Code
10mLightning Talk: Policy as [Versioned] Code - You're Doing It Wrong.
41mModern Policy Management Putting responsibility where it belongs
40mPolicyfiles
05mContinuously Update Everything
30mEnhance your Compliance with Policy-Based CI/CD
14mRisk Management in a Coded Enterprise