Repository navigation
v1.3.1
Changed
- Request/reply is now on by default for a cluster. Every existing agent stays
off after the upgrade — an agent only accepts requests once you turn it on.
Added
- A per-agent request/reply switch, in Agent Details and on the create/read/patch
API (spec.requestReplyEnabled). Turning an agent off rejects new requests
with a stable error; requests already in flight still complete.
Callers still need requests:write / requests:read. Redis stays required, and
the API fails closed without it.