b71375fac7
This was mostly affecting the stream writer (events) worker, which was being reported as unhealthy. It wasn't causing any issues, but it just looked odd and was confusing people. As an alternative to hitting the regular `/health` healthcheck route (on the "client" API which this stream writer does not expose), we may have went for hitting some "replication" API endpoint instead. This is more complicated and likely unnecessary. |
||
|---|---|---|
| .. | ||
| defaults | ||
| tasks | ||
| templates | ||
| vars | ||