mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

docs: reword the set-key note without passive voice

Browse source
This commit is contained in:
iris 2026-11-11 18:34:40 +01:00 • committed by mara
commit 119e225c17
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/2-handbook/swarm/services.md
View file

@ -353,7 +353,7 @@ below). Set `deploy.review-classifier.enable` directly to override either way.
The operator sets the key of the runtime the swarm settings choose in the The operator sets the key of the runtime the swarm settings choose in the
swarm UI: the **classifier settings** card on `/jobs` takes a key for the swarm UI: the **classifier settings** card on `/jobs` takes a key for the
chosen runtime and shows whether one exists and when it changed, never the chosen runtime and shows whether one exists and when it changed, never the
key. "Set" means a key was written, not that it works: a run with a bad key key. "Set" means a key exists, not that it works: a run with a bad key
still fails. You can also write the same two keys in the secret store's UI under the still fails. You can also write the same two keys in the secret store's UI under the
OIDC login, field `api_key`: OIDC login, field `api_key`:

2
docs/4-implementation/swarm/review-classifier.md
View file

@ -310,7 +310,7 @@ a runtime that isn't one of the two or a refused key, **401** for no
`Remote-User`, **503** when the store is unreachable or refuses. `Remote-User`, **503** when the store is unreachable or refuses.
`set` means the leaf's metadata exists. It doesn't mean the key works: a leaf `set` means the leaf's metadata exists. It doesn't mean the key works: a leaf
written by hand under another field name, or one whose latest version was written by hand under another field name, or one with its latest version
deleted, still shows as set, because the controller can't read a value to check. deleted, still shows as set, because the controller can't read a value to check.
The classifier reads the leaf on every run, so a new key applies from the next The classifier reads the leaf on every run, so a new key applies from the next