Intent
Use a canonical reference configuration as the source of truth for validation and enforcement.
When to use
- Multiple environments must stay aligned.
- Compliance requires a clear baseline.
- Automation needs a definitive desired state.
Core mechanics
- Define the reference config and schema.
- Store it in version control.
- Compare live state to the reference and apply deltas.
Implementation checklist
- Document the reference config and schema.
- Version the reference in the repo.
- Define environment overrides explicitly.
- Build validation and diff checks.
- Schedule regular compliance reviews.
Failure modes and mitigations
- Outdated reference -> review on a defined cadence.
- Hidden overrides -> document and enforce override rules.
- Manual edits -> detect drift and alert.
Observability and validation
- Diff counts and compliance status per target.
- Last reviewed date and version.
Artifacts
- Reference config file.
- Schema documentation.
- Diff report.