Destroy selected pipelines while preserving their managed sources and replay data:
Reset all StreamBuild-managed pipeline and source relations in one target:
Standalone destructive commands resolve the local OS username in the same StreamBuild account
control store used by the development server. The account must be active and hold the built-in
admin role. Use --control-store-url when the installation does not use the project-local default
store.
The frozen plan and review lifecycle use the durable relational control store rather than
process-local memory. Immediately before execution, StreamBuild reloads the account, recompiles the
project, resolves the selected target’s physical database again, and rejects account, target, or
database drift.
Both commands:
- require an interactive stdin terminal
- print the complete frozen impact plan before prompting
- require a separate review decision
- prompt separately for every exact, case-sensitive challenge value
- use the same planner, target lock, drift checks, executor, and operation recording as the UI
The commands do not accept non-interactive output or approval options. In particular, there is no
--yes, --force, --auto-approve, --confirm, --apply, or --no-confirm option.
Destruction is irreversible. A later build can recreate authored resources, but StreamBuild does
not restore the dropped data or automatically roll back a partial failure.
See Destructive Operations for exact resource scope,
confirmation rules, dependency closure, and retained evidence.