Validate preview requests before allocating resources
A branch name containing slashes and punctuation becomes an invalid database name after resources are already created.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Validation · Resource naming
Estimated field mix
- Platform engineering60%
- API design20%
- Security20%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Use an opaque environment ID for resource names.
- Validate repository scope, revision and requested lifetime.
- Reject malformed requests before any provider call.
Implementation constraints
- Treat branch labels as display data only.
Verification to include
- Accept a valid synthetic revision with a complex branch label.
- Reject missing scope and excessive lifetime with zero allocation calls.
Deliverables
- Preview request schema
Rollout and recovery
Enable request validation first; leave rejected previews unallocated.
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.