Installed Plugins
Hegemony's capabilities are extended by plugin packages - Python wheels installed alongside the platform. Settings → Installed Plugins shows what this instance has: every discovered package and every type it registers, grouped by subsystem.
The six plugin subsystems
| Group | Adds |
|---|---|
| Step handlers | Step types available in the flow editor's handler catalog. |
| Inventory providers | External inventory sources (NetBox and similar) that sync sites, devices, and other object types. |
| Notification transports | Ways to deliver notifications (email, chat services, webhooks). |
| Secret backends | Places secrets can be stored and resolved from. |
| Probes | Check types used by connectivity monitors. |
| Device transports | How CLI steps talk to devices (for example netmiko for network gear, asyncssh for Linux hosts). |
Each package shows its version and a health badge: Loaded means the running process matches what is on disk; Restart required means a newer version was installed but the process still runs the old one.
Expand any registered type to see its description, capabilities, and configuration fields - useful when filling in provider or destination forms elsewhere in Settings.
This page is read-only
Plugins are not installed or removed here. They are installed as Python wheels in the API and worker environments by whoever operates the deployment - and both must have the same wheels. After installing or upgrading, restart the API and the workers so each registry reloads; until then the page shows Restart required.
The API refuses to save, import, or restore into the draft a flow with a step whose handler is not installed on the API (400, naming the step and the handler), because it cannot check such a step's container options. A flow saved earlier stays readable; install the wheel on the API before editing it.
Where plugin types show up
- Step handlers appear in the flow editor's handler picker and in the step handler reference; a handler whose wheel ships a documentation page renders it in the Help drawer's Installed Handlers topic, clearly framed as the plugin's own content; the step editor's Handler tab links straight to it.
- Inventory provider types appear when creating a provider under Settings → Inventory Providers.
- Notification transport types appear when creating a destination on the Notifications screen - see notifications.
- Secret backend types appear under Settings → Secret Backends - see secrets.
Viewing this page requires the plugin:view action (granted to the operator role by default; reallocatable under Settings → Permissions → Actions).