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

docs: a classifier key shown as set may still not work

Browse source 
The controller can only see that the leaf exists, so a key under the wrong field name or a deleted latest version still shows as set.
This commit is contained in:
iris 2026-11-11 18:33:22 +01:00 • committed by mara
commit 2370f99229
1 changed files with 6 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -309,6 +309,10 @@ the key. Every error is problem+json: **400** for a body that isn't this shape,
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.
`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
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
run. The operator can still write the leaves in the secret store's UI
([`services.md`](../../2-handbook/swarm/services.md#review-classifier)).