Enforce preview quotas across concurrent requests
Two valid plans each fit the remaining quota, then apply concurrently and exceed the team limit together.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Concurrency · Leases · Quota enforcement
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
- Quota reservation and environment admission are atomic
- Expired reservations are reclaimed through identity-checked leases
- Provider failure releases or reconciles reservation deterministically
Implementation constraints
- Do not hold a database transaction open across provider operations.
Verification to include
- Admit concurrent plans whose combined cost fits exactly.
- Race two plans over the limit and verify only one obtains authority to apply.
Deliverables
- Quota reservation protocol and concurrency tests
Rollout and recovery
Start with conservative team quotas and visible denials.
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.