Gate promotion on database compatibility
A release expects a renamed column while rollback still expects the old one, making the nominal rollback artifact unusable.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Database migrations · Compatibility · Rollback planning
Estimated field mix
- DevOps60%
- Database engineering40%
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 API is rebuilt separately for test, staging, and production-like local environments. The resulting images differ, release notes list the branch instead of the artifact, and rollback rebuilds old source with new dependencies. Use a local registry simulator and synthetic deployments; no cluster or customer traffic is supplied.
Setup prerequisites
- Artifact digests
- Release states
- Health checks
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Manifest declares required and provided schema compatibility window
- Promotion checks current environment schema before deployment
- Rollback target is validated against post-migration schema
Implementation constraints
- Use fixture schema versions; do not execute migrations against a real database.
Verification to include
- Promote an expand-compatible release and validate its rollback target.
- Attempt a contract-first release and show the gate identifies the incompatible direction.
Deliverables
- Schema compatibility gate and rollout matrix
Rollout and recovery
Require expand, migrate, contract phases for destructive changes.
Value of the work
For the engineer: Practice immutable promotion, release authority, compatibility gates, canaries, and rollback.
For the team: Review a delivery flow that can identify exactly what is running and restore a known artifact without rebuilding it.
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.