docs: describe the create-agent dialog's hive and permission load failures
This commit is contained in:
parent
46a6fc36d8
commit
803ba01372
1 changed files with 4 additions and 0 deletions
|
|
@ -432,6 +432,10 @@ as optional `limits` and `inference` objects, the same shapes the two `PUT`
|
||||||
routes take. The controller checks them with the `PUT` rules before it queues
|
routes take. The controller checks them with the `PUT` rules before it queues
|
||||||
anything, so a bad value gets a refusal with its reason and creates no agent.
|
anything, so a bad value gets a refusal with its reason and creates no agent.
|
||||||
|
|
||||||
|
The dialog loads the hive list and the permission list when it opens. If either
|
||||||
|
load fails, the dialog says why in place of an empty picker, with the text
|
||||||
|
`could not load hives` or `could not load permissions`.
|
||||||
|
|
||||||
It stores them ahead of the job graph, before it declares the agent, so they
|
It stores them ahead of the job graph, before it declares the agent, so they
|
||||||
are in place before the agent first runs. If the creation then fails, the
|
are in place before the agent first runs. If the creation then fails, the
|
||||||
controller puts back what it replaced. Each agent name keys its settings and
|
controller puts back what it replaced. Each agent name keys its settings and
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue