Pipeline
Synopsis
Executes another pipeline by name, allowing for pipeline reuse and modular configurations.
Schema
- pipeline:
name: <string>
description: <text>
if: <script>
ignore_failure: <boolean>
ignore_missing_pipeline: <boolean>
on_failure: <processor[]>
on_success: <processor[]>
tag: <string>
Configuration
The following fields are used to define the processor:
| Field | Required | Default | Description |
|---|---|---|---|
name | Y | - | Name or reference of the pipeline to execute |
description | N | - | Explanatory note |
if | N | - | Condition to run |
ignore_failure | N | false | See Handling Failures |
ignore_missing_pipeline | N | false | If true, silently continue when referenced pipeline is not found |
on_failure | N | - | See Handling Failures |
on_success | N | - | See Handling Success |
tag | N | - | Identifier |
Details
The pipeline processor can reference other pipelines using the syntax {{ IngestPipeline "pipeline-name" }}. The names can be specified with or without the .yml/.yaml extension.
As pipeline references are resolved at runtime, make sure all referenced pipelines exist in your configuration, or set ignore_missing_pipeline to true if they are optional.
The processor detects circular pipeline references at runtime. If a pipeline cycle is detected, the processor returns an error identifying the pipeline that caused the cycle.
Examples
Basic
Another pipeline to be executed... | |
must be defined in the configuration: | |
Conditionals
Executing the pipeline based on criteria... | |
helps control the flow: | |
Error Handling
Handle missing pipelines... | |
and specify fallback actions: | |