Display the exact release identity in diagnostics
Two API instances report version latest even though only one received yesterday's build. On call cannot connect a failing request to its deployed artifact.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Artifact provenance · Configuration · Diagnostics
Estimated field mix
- Platform engineering70%
- Site reliability30%
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 scheduling service has an API, a worker, and PostgreSQL. Releases use immutable images on two application instances. The team needs compatibility checks, staged traffic, and a rehearsed rollback without introducing a new orchestration platform.
Setup prerequisites
- HTTP health checks
- CI pipelines
- Database migrations
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Expose build revision, immutable artifact digest, and deployment ID through an authorized diagnostic endpoint.
- Fail validation when a release manifest lacks immutable identity.
- Keep build secrets and environment values outside the response.
Implementation constraints
- The build injects identity; request parameters cannot override it.
Verification to include
- Read distinct diagnostics from two synthetic release versions.
- Reject a manifest containing only a mutable tag and inspect response redaction.
Deliverables
- Release manifest schema and diagnostic projection
Rollout and recovery
Add diagnostics before changing deployment routing; remove endpoint exposure without changing artifact identities.
Value of the work
For the engineer: Practice release contracts, compatibility windows, measurable canaries, and incident decisions on a modest application topology.
For the team: Review whether an engineer can make deployments diagnosable and reversible while identifying when rollback is unsafe.
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.