stackblaze pipelines

A pipeline is a project; its phases are environments. Alias: pipeline.

Usage

stackblaze pipelines list
stackblaze pipelines create -p <name> [--phases <names...>] [--domain <host>]
stackblaze pipelines delete [name] [-y]

Subcommand	Description
list	Pipelines and their phases (also stackblaze list)
create	Create a pipeline named by --pipeline
delete [name]	Delete a pipeline and all its apps (default: the linked pipeline); asks you to type its name unless -y

Flag	Applies to	Description
--phases <names...>	create	Phases to create (default production)
--domain <host>	create	Wildcard domain for the pipeline’s apps
-y, --yes	delete	Skip the confirmation

Every subcommand accepts the scope and output flags: -p, --pipeline, --phase, -a, --app, --token, --api-url, -o, --output, --json.

delete takes the pipeline as a positional name or --pipeline (passing both with different values is an error). Without either, it targets STACKBLAZE_PIPELINE or the linked pipeline, names it on stderr, and still asks you to type the name unless -y. When the deleted pipeline is the linked one, .stackblaze/project.json is removed. With -o json the result is {"deleted": true, "pipeline": "…"}. Check the target with stackblaze context first.

Examples

stackblaze pipelines create -p shop --phases staging production
stackblaze pipelines delete shop-old -y

To create a pipeline and link the directory in one step, use stackblaze init.