Keep preview connection material out of build output
Provisioning logs print database URLs that contain temporary credentials.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Secrets handling · Logging
Estimated field mix
- Security60%
- Platform engineering40%
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
- Redact passwords, tokens and credential-bearing URLs.
- Return secret references separately from public preview metadata.
- Keep synthetic credentials out of generated manifests.
Implementation constraints
- Use allowlisted structured logging fields.
Verification to include
- Inspect successful provisioning logs for safe identifiers.
- Inject a credential into provider errors and assert redaction.
Deliverables
- Log redaction and metadata projection
Rollout and recovery
Deploy redaction before provisioning; rotate any affected disposable credentials.
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.