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 the operator runs 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 the pipeline developer assembles into stages and pipelines. Task work is packaged into content packs for delivery to the administrator.
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 the operator can classify and configure machines consistently.
Integration Developer
Extends DRP into external systems using the REST API, drpcli, or the plugin system. The integration
developer connects 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¶
The Pipeline Developer, Task Developer, and Hardware Developer package their work as content packs for distribution. See the Content Packs section for how to generate, bundle, and deliver content to the administrator.
To promote content created directly in the DRP UX (BackingStore read/write objects) into a versioned content bundle, see Converting Read/Write Objects to Content Bundles.