Detect environment drift without copying secret data
A local environment's retry count is changed outside the compiler, but drift reports are disabled because teams fear dumping secrets.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Drift detection · Redaction · Reconciliation
Estimated field mix
- DevOps70%
- Platform engineering30%
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
- Compare ordinary canonical values and secret reference identities
- Report missing, extra, and changed paths with provenance
- Secret values and provider error bodies are never serialized
Implementation constraints
- Observed configuration comes from a bounded fake runtime projection.
Verification to include
- Detect changes in an ordinary value and a secret reference version.
- Return a sentinel secret in observed input and prove it cannot enter the report.
Deliverables
- Redacted drift detector and fixture report
Rollout and recovery
Begin in read-only mode and resolve unexplained differences before automation.
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.