docs: a classifier key shown as set may still not work
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:
parent
6875a4f0f8
commit
2370f99229
1 changed files with 6 additions and 1 deletions
|
|
@ -353,7 +353,8 @@ 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
|
||||
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
|
||||
key. You can also write the same two keys in the secret store's UI under the
|
||||
key. "Set" means a key was written, 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
|
||||
OIDC login, field `api_key`:
|
||||
|
||||
- the API key runtime's Anthropic key at
|
||||
|
|
|
|||
Loading…
Reference in a new issue