docs: clear the vale errors the queue-credential prose introduced
`vale --minAlertLevel=error docs` is a CI gate and origin/main passes it with zero findings, so the twelve this branch added were a red build, not a backlog: eight Microsoft.Contractions, one write-good.So, two write-good.Passive, across the new credential-matrix row, the backfill runbook and the mint-identity help text. Contractions and the sentence that started with "So" are mechanical. The two passive hits are rewrites: "`--hive` is required" becomes "`--hive` has no default", which is the actual claim -- the flag has no value to fall back on -- and the help text's "the agent's queue secret is left exactly as it is" becomes "it leaves an existing queue secret exactly as it stands", which also names who does the leaving. docs/tools/swarmctl-cli.md is regenerated, not hand-edited; the wording lives in swarmctl's clap doc comments.
This commit is contained in:
parent
8b6dc72526
commit
10427467b3
3 changed files with 23 additions and 24 deletions
|
|
@ -83,7 +83,7 @@ Queue a re-mint of an existing agent's identity at the swarm's secret store.
|
|||
|
||||
**The backfill verb.** Agent creation is event-driven and nothing at swarm level sweeps for agents that are missing a credential, so an agent created before a credential joined the mint never receives one. This re-runs the mint for one agent that already exists.
|
||||
|
||||
⚠️ **It re-mints the agent's store certificate**, which that agent picks up the next time its container boots. The agent's queue secret is left exactly as it is if it already has one, so running this against an already-migrated agent does not disturb its queue connection.
|
||||
⚠️ **It re-mints the agent's store certificate**, which that agent picks up the next time its container boots. It leaves an existing queue secret exactly as it stands, so running this against an already-migrated agent doesn't disturb its queue connection.
|
||||
|
||||
Queues and returns, the same way `agent create` does — watch the swarm UI's job view for the outcome.
|
||||
|
||||
|
|
@ -97,7 +97,7 @@ Queues and returns, the same way `agent create` does — watch the swarm UI's jo
|
|||
|
||||
* `--hive <HIVE>` — The hive that agent runs on.
|
||||
|
||||
Required, and deliberately not defaulted: the credentials this mints name a hive, and neither this CLI nor the controller keeps a roster of which agent is on which hive. Naming the wrong one gives the agent an identity scoped to a hive it does not run on. The controller checks the value against the swarm's hive roster and names the known hives if it misses.
|
||||
Required, and deliberately not defaulted: the credentials this mints name a hive, and neither this CLI nor the controller keeps a roster of which agent is on which hive. Naming the wrong one gives the agent an identity scoped to a hive it doesn't run on. The controller checks the value against the swarm's hive roster and names the known hives if it misses.
|
||||
* `--controller-socket <PATH>` — swarm-controller's unix socket.
|
||||
|
||||
Supplied by the nix module that installs this binary, from the same `socketPath` option the daemon binds; falls back to `SWARM_CONTROLLER_SOCKET`.
|
||||
|
|
|
|||
Loading…
Reference in a new issue