EXTENSIONS
Extensions package reusable automation into installable units. Each extension contains one or more content types — models, workflows, vaults, datastores, drivers, and reports — declared in a manifest.
Content Types
| Type | Purpose | Export | File location |
|---|---|---|---|
| Model | Resource lifecycle automation | model |
extensions/models/ |
| Workflow | Multi-step orchestration | YAML | extensions/workflows/ |
| Vault | Secret storage backend | vault |
extensions/vaults/ |
| Datastore | Data persistence backend | datastore |
extensions/datastores/ |
| Driver | Out-of-process execution runtime | driver |
extensions/drivers/ |
| Report | Post-execution analysis | report |
extensions/reports/ |
TypeScript content types (model, vault, datastore, driver, report) export a named object that swamp loads at runtime. The export shape and provider interface for each type is documented in the pages below.
In This Section
- Manifest — YAML schema for
manifest.yaml - Management — CLI commands for installing, updating, and searching extensions
- Scorecard Rubric — quality scoring factors and grade thresholds
- Vault Provider — interface for custom secret storage backends
- Datastore Provider — interface for custom data persistence backends
- Driver — interface for custom execution runtimes
- Model — interface for resource automation models
- Report — interface for post-execution analysis