Publish the preview URL only after identity-aware readiness
The bot posts a URL when the load balancer responds, but it points to an older preview that still owns the recycled alias.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Readiness · DNS · Identity validation
Estimated field mix
- DevOps70%
- Networking30%
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.
- DPREVIEW-101 · Derive a collision-resistant preview identity
- DPREVIEW-102 · Compile a minimal preview configuration
- DPREVIEW-103 · Plan the resource graph before creating anything
- DPREVIEW-104 · Apply preview resources idempotently after interruption
- DPREVIEW-105 · Seed representative data without copying customer records
Acceptance criteria
- Readiness proves environment ID, revision, schema, and seed version
- URL publication compares alias ownership immediately before update
- Failure remains pending or failed with exact dependency status
Implementation constraints
- Use fake DNS and loopback probes; no public record is created.
Verification to include
- Publish a ready matching preview alias.
- Return healthy content from an older environment and block publication.
Deliverables
- Identity-aware readiness gate and stale-alias test
Rollout and recovery
Show URLs only after the new gate succeeds.
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.