Keep environment-specific settings outside immutable application bytes
The team rebuilds the same release for staging and production, making tested bytes differ from deployed bytes.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Deployment design
Estimated field mix
- Platform engineering50%
- Cloud infrastructure50%
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 application team deploys mutable image tags and cannot reliably identify the artifact running during an incident.
Setup prerequisites
- Author synthetic artifact manifests and a local registry double; do not pull or execute untrusted images.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Use one application digest across modeled environments.
- Bind runtime configuration separately.
- Validate required configuration without embedding secrets.
Implementation constraints
- No actual cloud deployment is required.
Verification to include
- Promote the same digest through two synthetic environments.
- Reject a configuration missing a required setting.
Deliverables
- Artifact/configuration boundary.
Rollout and recovery
Adopt on one service; retain previous configuration versions for recovery.
Value of the work
For the engineer: Practice artifact identity, promotion policies, and release provenance.
For the team: Provide reproducible deployments and a clear path to withdraw defective artifacts.
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.