swarm ui ssh row with target snippets, docs for the per-agent switch
This commit is contained in:
parent
624d5f24f8
commit
e621397252
1 changed files with 417 additions and 94 deletions
|
|
@ -851,6 +851,17 @@ back, so the controller's log (`agent max repos`) is the record of what it appli
|
|||
to each agent. The controller tries an agent whose account the forge refuses again
|
||||
every five minutes.
|
||||
|
||||
The **ssh** row is whether the agent may get SSH certificates from the swarm: a
|
||||
badge reading on or off, off by default. Selecting it opens an explainer, a
|
||||
checkbox that does a `PUT` of `ssh` with the stored permissions beside it, and
|
||||
a folded **on the target** section. That section reads `GET /api/ssh/ca` and
|
||||
shows the swarm's CA key and the agent's name as the lines for a NixOS machine,
|
||||
a home-manager user and a plain `authorized_keys` file, with a copy button; the
|
||||
card builds the text in `frontend/packages/swarm-ui/src/agent/detail/ssh.ts`. A `PUT`
|
||||
that leaves `ssh` out, and the `DELETE` of **use the default**, keep it. The
|
||||
controller attaches the signing policy to the agent's login role within five
|
||||
minutes; see [the SSH CA](../swarm/ssh-ca.md#the-switch-and-the-signing-policy).
|
||||
|
||||
A saved change isn't instant. The hive reads the grant about every 30 seconds
|
||||
and the agent takes it at its next turn. A change to `manage_root_agent`
|
||||
restarts the agent after its current turn. The card reads
|
||||
|
|
|
|||
Loading…
Reference in a new issue