Feature Request Checklist
Problem Description
The /v1/events (SSE) endpoint only emits scan_started/scan_completed events when a run goes through the update path (POST /v1/update, or the internal scheduled --interval/--schedule run). A registry check triggered via POST /v1/check produces no SSE event at all.
I would like to check for updates from homeassistant integration which I'm creating right now and would like to be notified about finished checks so I can reload state of entities.
Desired Solution
Emit an event (either the existing scan_started/scan_completed pair, or new check_started/check_completed events, whichever fits Watchtower's internal model better) whenever POST /v1/check or scheduler runs a registry check. This would let SSE subscribers know a check just completed and that they should refresh their view (via /v1/containers/details), without falling back to polling on a fixed interval - which is exactly what a push-based /v1/events endpoint is meant to avoid.
Current Alternatives or Workarounds
The only current workaround is polling /v1/containers/details on a fixed client-side interval, which defeats the purpose of having /v1/events for this use case.
Additional Context
This came up while building a Home Assistant integration on top of the HTTP API. /v1/check is used specifically because it doesn't perform an update - the intent is to let the user review availability and press an explicit "Update" button - so the lack of events on check-only runs is a real gap for anything built around that pattern.
Feature Request Checklist
Problem Description
The
/v1/events(SSE) endpoint only emitsscan_started/scan_completedevents when a run goes through the update path (POST /v1/update, or the internal scheduled--interval/--schedulerun). A registry check triggered via POST/v1/checkproduces no SSE event at all.I would like to check for updates from homeassistant integration which I'm creating right now and would like to be notified about finished checks so I can reload state of entities.
Desired Solution
Emit an event (either the existing
scan_started/scan_completedpair, or newcheck_started/check_completedevents, whichever fits Watchtower's internal model better) wheneverPOST /v1/checkor scheduler runs a registry check. This would let SSE subscribers know a check just completed and that they should refresh their view (via/v1/containers/details), without falling back to polling on a fixed interval - which is exactly what a push-based/v1/eventsendpoint is meant to avoid.Current Alternatives or Workarounds
The only current workaround is polling
/v1/containers/detailson a fixed client-side interval, which defeats the purpose of having/v1/eventsfor this use case.Additional Context
This came up while building a Home Assistant integration on top of the HTTP API.
/v1/checkis used specifically because it doesn't perform an update - the intent is to let the user review availability and press an explicit "Update" button - so the lack of events on check-only runs is a real gap for anything built around that pattern.