Apply preview resources idempotently after interruption
Provisioning stops after database creation. Retry creates a second database because local state was not saved before the provider call.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Idempotency · Infrastructure automation · Recovery
Estimated field mix
- DevOps60%
- Distributed systems40%
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
- Each resource has deterministic operation identity
- Apply reconciles provider state before create
- Completed resources resume without recreating or skipping dependencies
Implementation constraints
- Provider calls execute outside state transactions and return untrusted observations.
Verification to include
- Apply a complete plan and replay it without changes.
- Interrupt after one accepted create and confirm retry adopts the matching resource.
Deliverables
- Idempotent preview applier and interruption drill
Rollout and recovery
Limit concurrent previews while reconciliation behavior is observed.
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.