Flows
A flow is a Camel route, plus its visual layout, plus its parameters. It’s the unit you author in the designer and deploy to a runtime.
Anatomy
Section titled “Anatomy”| Piece | What it is | Where it lives |
|---|---|---|
| YAML | Camel route definition (canonical) | flow.camel.yaml on the designer’s disk |
| Layout | BPMN shapes + edges + extras (visual only) | flow.layout.json |
| Params | {{key}} placeholders substituted at deploy time | params.json |
The YAML is the source of truth. Camel reads YAML; the designer reads both YAML and layout to render the canvas.
Status
Section titled “Status”A flow’s status is derived from its deployment matrix — not stored on the flow itself:
- Healthy — every registered runtime has the flow
in-sync - Warning — at least one runtime has the flow
stale(local edits not yet redeployed) - Failed — every runtime is
unreachableor returned an error - Draft — the flow exists in the designer but is on no runtime yet
- Paused — operator manually disarmed it (not automatic)
Lifecycle
Section titled “Lifecycle”- Create via
+ New flow— lands as Draft - Edit in the designer — Save writes YAML + layout to disk
- Deploy to a runtime — pushes YAML via
PUT /_api/flows/:id, runtime hot-reloads the route - Promote to downstream environments — same deploy mechanism, targets a different runtime
- Delete — removes from designer disk; cascade-undeploys from every runtime