Developer Guide¶
The Developer Guide is organized around developer personas — what you are building and who you are building it for. Choose the section that matches your role.
Note
The documentation is organized around user roles.
- Administrator Guide
- Architect Guide
- Developer Guide — you are here
- Operator Guide
- Resources
Developer Personas¶
Pipeline Developer Builds reusable automation pipelines — sequences of stages and tasks — that operators run against machines. Pipeline work is packaged into content packs and delivered to an administrator for deployment to a DRP endpoint or manager catalog.
Task Developer Builds the atomic units of work (tasks and templates) that pipeline developers assemble into stages and pipelines. Task work is packaged into content packs for delivery to administrators.
Hardware Developer Baselines physical machines and generates hardware profiles that encode hardware-specific configurations (BIOS, RAID, NIC). Hardware work is packaged into content packs so operators can classify and configure machines consistently.
Integration Developer
Extends DRP into external systems using the REST API, drpcli, or the plugin system. Integration
developers connect DRP to CI/CD pipelines, orchestration platforms, CMDBs, and other tools.
Foundational Skills¶
All developer personas benefit from familiarity with the DRP CLI and API:
- How to Use the CLI —
drpcliscripting, filtering, reporting, and call examples - How to Use the API — REST API reference, Swagger, language clients (Go, Python)
Delivering Content¶
Pipeline, Task, and Hardware Developers package their work as content packs for distribution. See the Content Packs section for how to generate, bundle, and deliver content to administrators.