Resolve secret rotation without restarting into a mixed revision
Two secret references rotate independently while workers reload, leaving some requests signed with mismatched key and certificate versions.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Secret rotation · Atomic publication · Concurrency
Estimated field mix
- DevOps65%
- Security35%
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
- Dependent secret references resolve as one declared bundle revision
- Reload publishes only a fully validated immutable snapshot
- In-flight work retains its starting snapshot until completion
Implementation constraints
- Fake secret material stays inside the local adapter and is never included in generic configuration hashes.
Verification to include
- Rotate a complete bundle while old and new operations overlap.
- Withhold one member and confirm no worker selects the partial revision.
Deliverables
- Secret-bundle reload protocol and overlap test
Rollout and recovery
Keep restart-based rotation available until snapshot reload is proven.
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.