Plan the resource graph before creating anything
Provisioning creates storage before discovering the requested database class exceeds the preview quota, leaving an orphan.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Infrastructure planning · Quotas · Dependency graphs
Estimated field mix
- DevOps60%
- Cloud infrastructure40%
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
- Plan resolves complete dependency graph and quota cost
- Validation lists every blocking reason before mutation
- Plan has immutable revision used by apply
Implementation constraints
- Fake provider discovery is read-only and bounded.
Verification to include
- Plan a valid preview and reconcile its declared resource order.
- Exceed compute and storage quotas together and confirm zero creates.
Deliverables
- Preview planner and multi-error quota tests
Rollout and recovery
Expose plan-only operation before apply is enabled.
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.