Create a review-environment resource plan with an explicit quota
One preview requests every optional dependency and exhausts the local resource budget.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Capacity planning · Resource limits
Estimated field mix
- Platform engineering60%
- 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 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.
Acceptance criteria
- List CPU, memory, storage and lifetime requirements.
- Reject plans exceeding per-environment or aggregate quotas.
- Keep optional dependencies explicit rather than provisioned by default.
Implementation constraints
- Use documented synthetic quotas and a dry-run planner.
Verification to include
- Plan a minimal API and database preview.
- Exceed storage and concurrent-environment quotas and reject allocation.
Deliverables
- Quota-aware plan command
Rollout and recovery
Expose dry-run plans first; reduce admitted previews if available resources shrink.
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.