Events are written by the orchestrator as state changes. The full list:Documentation Index
Fetch the complete documentation index at: https://docs.slipway.sh/llms.txt
Use this file to discover all available pages before exploring further.
| Kind | Phase | When | Payload |
|---|---|---|---|
queued | queued | Deployment row created. | — |
secrets_resolved | queued | Spec parsed; secret references looked up. | { secrets: [{name, scope, source}, ...] } — never values |
vars_resolved | queued | Variable references looked up. | { vars: [{name, scope, source, value}, ...] } — values included |
registries_resolved | queued | Private-registry credentials assembled. | { registries: [...] } |
build_start | building | Build Job submitted, or cache lookup started. | — |
build_end | building | Build finished — freshly built or cache hit. | — |
deploy_start | deploying | Applying tenant workloads. | — |
cutover | deploying | A public service’s Ingress is live. | — |
healthy | healthy | Every public service is Ready. | — |
failed | terminal | Build, deploy, or healthcheck failed. | — |
cancelled | terminal | Cancelled — by user or by supersession. | — |
gc | terminal | Ephemeral TTL expired; namespace deleted. | — |
secrets_resolved and vars_resolved fire once per deploy each, even if the spec references nothing of that kind (in which case the events are skipped entirely).
build_start and build_end fire per buildable service — a spec with three buildable services emits three pairs of these events.
cutover fires once per public service, in alphabetical order by service prefix.