Bind preview URLs and callbacks to the environment origin
A preview callback redirects to an unrelated origin supplied in change metadata.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Origin security
Estimated field mix
- Security70%
- Cloud infrastructure30%
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 preview environments for pull requests. Forgotten environments accumulate cost, and shared test data leaks between reviews.
Setup prerequisites
- Author a local environment-provider double and synthetic pull-request events; provision no external resources.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Derive allowed origins from trusted environment state.
- Reject arbitrary redirect and callback destinations.
- Expire origin authority when the environment closes.
Implementation constraints
- Use local URLs and do not contact external hosts.
Verification to include
- Accept the environment's declared local callback.
- Reject a substituted external origin and stale environment.
Deliverables
- Origin binding guard.
Rollout and recovery
Expose preview links only after origin validation.
Value of the work
For the engineer: Practice resource lifecycle state machines, isolation, and reconciliation.
For the team: Make review environments predictable, isolated, and accountable to a budget.
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.