Pipeline Developer Guide¶
A Pipeline Developer builds reusable automation pipelines that the operator runs against machines. Pipelines define the sequence of operations — provisioning, configuration, validation, decommission — that DRP executes during a machine's lifecycle.
Pipeline work is packaged as content packs and delivered to an administrator, who deploys them to a DRP endpoint or publishes them to a manager catalog for distribution to the operator.
Delivering Your Work
The Pipeline Developer packages their work into content packs for delivery. See the Content Packs section for how to generate, bundle, and distribute your content.
What the Pipeline Developer Builds¶
- Pipelines — Named sequences of stages that define an end-to-end machine workflow
- Pipeline Elements — Reusable segments that can be composed into pipelines
- Stages — Discrete checkpoints within a workflow that group related tasks
- Workflows — Higher-level orchestration that chains pipelines together
- Triggers — Event-driven automation that fires pipelines in response to state changes
- Blueprints — Templates that define complete machine configuration patterns
Topics in This Section¶
- Pipeline Design — Patterns and best practices for designing pipelines
- Pipelines — Building and structuring pipelines
- Pipeline Elements — Creating reusable pipeline segments
- Workflows — Orchestrating multiple pipelines
- Stages — Defining stage checkpoints
- Triggers — Event-driven pipeline execution
- Blueprints — Machine configuration templates