Promote configuration by immutable revision
A mutable environment file changes after approval but before deployment, so the applied settings were never reviewed.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Content hashing · Immutable configuration · Authorization
Estimated field mix
- DevOps70%
- Security30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional notification service uses environment files assembled by shell scripts. Defaults differ by machine, secret values appear in diagnostics, and emergency flags have no expiry. Build a typed local configuration compiler with fake secret references and synthetic environments; no real credentials or notification providers are supplied.
Setup prerequisites
- Configuration precedence
- Schema validation
- Least privilege
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Compilation produces canonical content and immutable revision hash
- Approval and deployment bind the exact revision
- Any source-layer change produces a new revision
Implementation constraints
- Exclude secret values while binding secret reference identities and schema version.
Verification to include
- Approve and deploy one unchanged revision.
- Edit a source layer after approval and verify deployment refuses the stale authorization.
Deliverables
- Immutable configuration revision and approval-binding tests
Rollout and recovery
Use revision identities in the local deployment simulator before removing mutable file reads.
Value of the work
For the engineer: Practice configuration as a reviewed contract with safe diagnostics, provenance, and rollback.
For the team: Review environment changes before deployment and reduce outages caused by missing, stale, or silently defaulted settings.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.