Expire previews without deleting an active replacement
A delayed cleanup job for an old preview alias deletes storage now owned by a newer environment.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cleanup · Fencing · Resource ownership
Estimated field mix
- DevOps70%
- Cloud infrastructure30%
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 product team creates local preview environments for pull requests. Names collide, fixtures copy more data than needed, failed provisioning leaks resources, and merged changes leave previews running. Build an infrastructure simulator with fake DNS, storage, and deployment providers; no cloud account or live domain is supplied.
Setup prerequisites
- Resource graphs
- Idempotency
- Tenant isolation
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Cleanup binds immutable environment and resource identities
- Deletion compares current provider ownership before action
- Alias reuse cannot transfer cleanup authority
Implementation constraints
- Use fake providers and delete only resources returned by the scoped plan.
Verification to include
- Expire one environment and remove exactly its resource graph.
- Reuse its alias for a new environment before delayed cleanup and confirm new resources survive.
Deliverables
- Fenced expiry job and alias-reuse regression
Rollout and recovery
Run cleanup in report-only mode before enabling deletions.
Value of the work
For the engineer: Practice ephemeral environment lifecycle, scoped configuration, cleanup, quotas, and provider reconciliation.
For the team: Review changes in isolated representative environments while controlling leakage, resource growth, and abandoned infrastructure.
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.