swarm-controller: keep retrying the forge webhook secret and registration after a startup outage
The webhook secret slot is filled in the background, on the forge token's capped unbounded backoff, when the store can't answer at start. The hook registration waits for the secret and retries on the same backoff instead of giving up after five tries. Closes #6101
This commit is contained in:
parent
431cb6e77f
commit
68b38a9d44
1 changed files with 284 additions and 114 deletions
|
|
@ -484,6 +484,10 @@ To check it's working, push to `internal/knowledge` and look for
|
|||
`webhook: verified delivery` in `journalctl -u swarm-controller`. A
|
||||
refused delivery logs `webhook: refused delivery` with the reason.
|
||||
|
||||
The controller registers the hooks as soon as it has both the forge token and
|
||||
the secret, and keeps trying, at most five minutes apart, for as long as the
|
||||
forge or the secret store is down. A restart isn't needed to recover.
|
||||
|
||||
## Hives: the substrate
|
||||
|
||||
- **hive** — one host running `hive-c0re` and its agent containers
|
||||
|
|
|
|||
Loading…
Reference in a new issue