Expire review environments with a grace period and owner visibility
A preview remains allocated after its pull request closes because nobody owns the cleanup schedule.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Lifecycle design · Authorization
Estimated field mix
- Platform engineering60%
- Cloud infrastructure20%
- Security20%
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 team creates preview stacks for pull requests. Orphan databases consume resources and previews sometimes inherit settings intended for another branch.
Setup prerequisites
- Create a local provisioning adapter with synthetic repository events.
- Use isolated disposable resources and no production credentials.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- AENV-101 · Validate preview requests before allocating resources
- AENV-102 · Create a review-environment resource plan with an explicit quota
- AENV-103 · Keep preview connection material out of build output
- AENV-104 · Make preview creation resumable after a partial provider failure
- AENV-105 · Bind preview updates to the exact requested source revision
- AENV-106 · Initialize preview data from a synthetic schema contract
- AENV-107 · Probe readiness without accidentally validating only process liveness
Acceptance criteria
- Persist owner token, expiry instant and grace deadline.
- List expiring environments without exposing credentials.
- Allow authorized extension within the declared maximum lifetime.
Implementation constraints
- Use an injectable clock and synthetic ownership.
Verification to include
- Advance through expiry and grace states.
- Attempt extension by another owner and reject it.
Deliverables
- Expiry state model and owner view
Rollout and recovery
Enable expiry reporting before cleanup; extend only reviewed environments during adoption.
Value of the work
For the engineer: Practice resource lifecycle, reconciliation and least-privilege setup.
For the team: Review reliable preview workflows and accountable resource cleanup.
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.