swarmctl: interactive setup walks the first-run ceremony
swarmctl setup with no subcommand checks the setup status first, then takes the open steps one at a time: prompts for input, shows a running action as one live line, prints the store keys, root token and new password under a warning until the operator confirms, and names the deploy option for a step this host cannot do. It calls the code of bao init, bao grant-bootstrap, user add, forge make-admin, agent create, agent permissions set and agent set-state. Refuses without root or a terminal.
This commit is contained in:
parent
4fae6a7766
commit
44caa72c19
1 changed files with 2172 additions and 82 deletions
|
|
@ -8,6 +8,14 @@ required options, is [`nixos.md`](nixos.md).
|
|||
|
||||
Every command runs as **root on the host**.
|
||||
|
||||
**Or just run `swarmctl setup`.** It walks the steps below interactively as root: it checks
|
||||
where you stand first, so a rerun continues where it stopped; shows `Step n of N`; prompts for
|
||||
what each step needs; shows a running action as one live line; and prints the secrets you must
|
||||
record, such as the store's keys and root token, under a ⚠️ warning until you confirm you stored
|
||||
them. A step this host can't do, because it doesn't run that service, names the deploy option
|
||||
it needs and the host to run `swarmctl setup` on. Steps with no verb yet print their command and
|
||||
wait for you. The sections below are the same steps by hand.
|
||||
|
||||
Run `swarmctl setup status` at any point to see how far you have got. It lists
|
||||
the hand steps below, numbered 1 to 10 in the order the sections run them, marks
|
||||
each done, not done or unknown, and names the next one. It changes nothing.
|
||||
|
|
|
|||
Loading…
Reference in a new issue