Cutover parameters

A cutover is the operational moment when a flow goes live in a new environment. Pipebase tracks parameter values per-runtime per-flow so you can review what changes before it deploys.

The matrix

Each flow declares its {{token}} parameters once, then assigns values per runtime:

Key	Type	Description	Dev	Staging	Prod
salesforceHost	string	API host	acme--dev.sandbox…	acme--uat.sandbox…	acme.my…
dbPassword	secret	DB password	••••	••••	••••
partitions	number	Topic partitions	2	4	8

Empty cells block deploy to that runtime but not to others — you can deploy to staging while prod cells are still being filled.

Resolution order

Parameters resolve in this order at deploy time (later wins):

global default → runtime override → flow cutover value

If a {{token}} in the YAML has no value at any layer, deploy fails with a 400 listing the missing keys.

Promote

When you’re ready to push values up the chain (e.g. dev → staging), click Promote on the flow’s Cutover page. The modal shows a diff of what changes; you can override individual cells before confirming. Promote is an additive merge — keys that only exist in the target are preserved.

Secrets

Parameters typed as secret never store plaintext in cutover.json. Values are written to the configured SecretBackend (Vault, AWS Parameter Store, or filesystem in dev). Reveal requires admin role and is audit-logged.

Audit history

Every value change, declaration, and promote is logged with actor, timestamp, key, runtime, and old/new value. Secret value changes are logged as [secret-changed] rather than the value itself. The history sidebar on the flow’s Cutover page paginates through the last N entries.

Where to find it

• In the editor: open the “Cutover parameters” drawer (Parameters button in the toolbar). Same component in both the classic and next editors.
• Full-page: /edit/<flowId>/cutover — adds the history sidebar + Promote modal. Designed to be bookmarked and shared with ops folks.
• Org overview: /cutover — read-only table showing every flow’s status per runtime (green/yellow/red dots). Click a flow row to drill into its cutover page.

Related

• Runtimes — defines the columns in the matrix.
• Transport routes — defines the promote chain.
• Flows — what gets deployed onto runtimes.
• Promote to prod tutorial — worked example.