Resume partial preview deletion without losing unresolved resources
DNS deletion succeeds, storage deletion times out after acceptance, and the environment is marked deleted despite an unknown storage outcome.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Lifecycle state · Provider reconciliation · Recovery
Estimated field mix
- DevOps60%
- Site reliability40%
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.
- DPREVIEW-101 · Derive a collision-resistant preview identity
- DPREVIEW-102 · Compile a minimal preview configuration
- DPREVIEW-103 · Plan the resource graph before creating anything
- DPREVIEW-104 · Apply preview resources idempotently after interruption
- DPREVIEW-108 · Expire previews without deleting an active replacement
Acceptance criteria
- Deletion tracks each resource as pending, deleted, absent, failed, or unknown
- Retry reconciles unknown provider state before mutation
- Environment closes only when every resource reaches a resolved terminal state
Implementation constraints
- Unknown does not equal absent; provider responses remain untrusted until identity reconciliation.
Verification to include
- Delete a full graph and replay the job idempotently.
- Lose a storage-delete response and confirm the environment remains visibly unresolved.
Deliverables
- Deletion state machine and partial-failure drill
Rollout and recovery
Alert on aged unresolved cleanup rather than hiding it.
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.