add-pipeline-instance

Add Pipeline Instance

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. add-pipeline-instance vX.Y — recent: <summary>. Then proceed.

Add an independent runtime instance to an existing pipeline. Each instance runs the same DAG with its own state and config — a zone, a tenant, a case, a customer.

The pipeline is the DAG. The instance is who the DAG runs for.

Process

Step 1: Resolve pipeline + instance slug

Expect <pipeline-slug> <instance-slug> as positional args. If missing, prompt.

Validate:

• projects/<pipeline-slug>/pipeline.yaml exists (else suggest /add-pipeline).
• <instance-slug> matches ^[a-z][a-z0-9-]{1,40}$.
• projects/<pipeline-slug>/instances/<instance-slug>/ does not already exist (else refuse — picking a new slug, or use /pipeline-resume if you meant to reactivate).

Step 2: Optional — clone from an existing instance

If --from <existing-instance> was passed, copy that instance's config.yaml as the starting point. Useful when most fields are identical across tenants/zones.

SRC="projects/$PIPELINE/instances/$FROM/config.yaml"
[ -f "$SRC" ] || error "Source instance not found"
mkdir -p "projects/$PIPELINE/instances/$INSTANCE"
cp "$SRC" "projects/$PIPELINE/instances/$INSTANCE/config.yaml"

Otherwise, scaffold a minimal config.yaml:

# Instance config for <INSTANCE> in pipeline <PIPELINE>
status: active                  # active | inactive — controls whether heartbeat evaluates
name: "<Human Name>"

# Per-instance overrides — merge over pipeline.yaml defaults.
# Common keys: sources, tags, filters, schema, PIRs, target outputs.
# Add what your stages need:
overrides: {}

Step 3: Ask config questions

These are intentionally minimal — instance-specific fields depend on the pipeline. Ask only what the pipeline needs.

Q1 — Display name (free text)

• "Human-readable name for this instance."