mirror of
https://github.com/docker/compose.git
synced 2026-11-17 13:45:39 +00:00
The progress-event stream is a de-facto public surface: the TTY renderer, --progress plain (grepped by user scripts), --progress json (consumed by tools) and SDK EventProcessors all read it. Converging the two lifecycle engines without a written contract is how silent divergences happen. api.EventProcessor now documents the contract: ordering is per resource (global interleaving is explicitly not guaranteed), the typical per-resource progressions (Creating→Created, Starting→Started, Waiting→Healthy|Exited, ...), early termination through Error or Skipped-with-reason, and status texts as stable identifiers. An executor test records the stream through a real plan (wait node + enriched start) and asserts the per-resource progressions — the same kind of assertion the wider phase 1 will lean on. Validated design decision for #14081 (event parity contract). Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .. | ||
| api.go | ||
| api_test.go | ||
| context.go | ||
| env.go | ||
| errors.go | ||
| errors_test.go | ||
| event.go | ||
| labels.go | ||
| labels_test.go | ||