Prevent migration commands from targeting unapproved databases
An engineer copied a connection string from another terminal.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Configuration · Safety boundaries
Estimated field mix
- Developer tooling50%
- Security30%
- Database engineering20%
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 subscription service has accumulated migration scripts with unclear lock risks and no consistent rehearsal output.
Setup prerequisites
- Create a disposable local database with synthetic subscriptions and a separate scratch database; author all fixtures locally.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Require an explicit local target allowlist.
- Display sanitized target identity before rehearsal.
- Reject missing, remote, or ambiguous target configuration.
Implementation constraints
- Never print passwords or complete connection URLs.
Verification to include
- Accept the named scratch database.
- Reject a remote hostname and inspect sanitized errors.
Deliverables
- Target guard.
Rollout and recovery
Default to no execution until a local target is configured.
Value of the work
For the engineer: Practice migration tooling, lock reasoning, and clear developer feedback.
For the team: Provide reviewers with repeatable migration checks and explicit recovery limits.
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.