Follow-up to #4 after the first live rotation on ace: the jackett/sonarr/radarr/lidarr runtimes cached the key from the software's config at start ("not configured — events idle"); they now read MESH_<X>_API_KEY_FILE (the vault's file, mounted) first and restart on needs-api-key. qBittorrent's init adds WebUI\BanDuration=60 so a step carrying a stale value bans the mesh for a minute, not an hour.
Follow-up to #4 after the first live rotation on ace: the jackett/sonarr/radarr/lidarr runtimes cached the key from the software's config at start ("not configured — events idle"); they now read `MESH_<X>_API_KEY_FILE` (the vault's file, mounted) first and restart on `needs-api-key`. qBittorrent's init adds `WebUI\BanDuration=60` so a step carrying a stale value bans the mesh for a minute, not an hour.
The jackett, sonarr, radarr and lidarr runtimes discovered the key from
the software's config at start, so after a rotation they held the old one.
They now read the vault's file first and restart when it is remade.
qBittorrent's init sets WebUI\BanDuration=60 so a consumer's step still
carrying the previous value no longer locks the others out for an hour.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #4 after the first live rotation on ace: the jackett/sonarr/radarr/lidarr runtimes cached the key from the software's config at start ("not configured — events idle"); they now read
MESH_<X>_API_KEY_FILE(the vault's file, mounted) first and restart onneeds-api-key. qBittorrent's init addsWebUI\BanDuration=60so a step carrying a stale value bans the mesh for a minute, not an hour.