Skip to main content

Editing

The Pipeline Editor is a full-page workspace for editing a pipeline and its child pipelines. It opens each pipeline as a YAML tab, tracks unsaved changes per tab, and hosts an inline debugger so you can test edits without leaving the editor.

Accessing the Editor​

Navigate to Content Management > Pipelines, select a pipeline, then click Pipeline Editor in the pipeline detail header. The editor occupies the full page, separate from the detail tabs. Editing requires pipeline-edit permission; with read-only permission the editor opens but the YAML is not editable and no save control appears.

Layout​

The editor has three areas, plus an optional debugger pane:

  • Sidebar (left, collapsible) — a tree of the main pipeline and its child pipelines.
  • Tab bar (top) — one tab per open pipeline.
  • Editor panel — a YAML editor for the active tab.
  • Debugger pane (bottom, on demand) — an inline pipeline debugger that opens below the editor and can be resized.

Pipeline Tree​

The sidebar lists the pipeline hierarchy. The root node is labeled name (root), where name is the main pipeline; each child pipeline appears as a node beneath it. Click a node to open that pipeline in a tab.

Each node provides a copy control and a delete control. Use Add new child pipeline at the bottom of the sidebar to create a child pipeline. Toggle the sidebar with the Collapse sidebar / Expand sidebar control; when collapsed, the sidebar reduces to a narrow rail.

Editing Tabs​

Opening the main pipeline or a child pipeline adds a tab. The main pipeline's tab is labeled name (Root) and cannot be closed; child tabs show the child pipeline's name and can be closed individually.

A tab with unsaved edits is marked with a dirty indicator in place of its close control. Closing a tab that has unsaved changes opens a Close confirmation prompting Discard and close or Cancel; closing a tab with no unsaved changes closes it immediately.

Editing and Saving​

Each tab is a YAML editor for that pipeline's processor configuration. Pipeline and processor syntax is documented in Overview.

Click Save changes to save the active tab. The control is enabled only when the tab has unsaved edits. On save, the editor validates that:

  • the configuration includes a name field, and
  • the name uses only lowercase letters, digits, and underscores, up to 150 characters.

Saves use optimistic concurrency: if the pipeline was changed elsewhere since you opened it, the save is rejected and you are prompted to retry, so concurrent edits are not silently overwritten.

Child Pipelines​

Click Add new child pipeline in the sidebar and provide a name to create a child pipeline. The new pipeline is seeded with a starter configuration containing a single comment processor, and opens in its own tab ready to edit.

To remove a child pipeline, use the delete control on its tree node and confirm with Delete (or Cancel). Deleting a child pipeline also closes its tab.

Debugging in the Editor​

Click Debug in the editor header to open the inline debugger pane at the bottom of the page. It runs the pipeline against selected test data and reports how each processor transforms it, using the same dataset providers, environment variables, and node status indicators as the standalone debugger. Each editor tab keeps its own debugger state. For full details, see Debugging.

Closing the Editor​

Click the close control in the editor header to return to the pipeline detail view. If any open tab has unsaved changes, a Quit Pipeline Editor? confirmation appears, prompting Discard and quit or Cancel before the editor closes.