Configurations¶
A Configuration is a named container of versioned collector YAML plus the metadata Ampora needs to ship it safely to agents.
| Page | Use it for |
|---|---|
| Importing YAML | Paste, upload, or sync from Git |
| Pipeline visualizer | Read-first swimlane view |
| Visual editor (drawflow) | Drag-and-drop authoring |
| Validation & lint | Syntax, semantic, and tenant-rule checks |
| Diffs (textual & semantic) | Compare versions or assigned vs effective |
| Versions & lifecycle | Draft, Published, Archived |
YAML is the source of truth¶
Whatever you do in the visualiser or the visual editor, the YAML text remains canonical. Ampora never reformats YAML on round-trip; your comments, anchors, and ordering survive. The visualisations are derived from the YAML, never the other way around.
Where configurations come from¶
- UI authoring — paste, upload, or build with the visual editor.
- GitOps — registered Git source (GitOps tutorial).
- REST API — programmatic creation; the same endpoints back the UI.
UI-authored and GitOps-authored configurations are visually distinguishable — the latter has a "Managed by GitOps" banner and the editor is read-only.