jschoubben
8ceec32692
A node carries its operator account (name + home; migration 0036, Node.Account,
SetAccount, 'node account' CLI). The account and its home are offered as
machine facts ${machine:account} / ${machine:account-home}, and machineInto
now resolves placeholders in a resource's path and owner (not just content), so
a module writes into a person's home naming what it cannot know. A RosterFile
gains Home: the file is placed under the account's home and chowned to it, its
template sees each node's Account, and a machine with no account gets none —
this is how the ssh Host blocks for every node reach a person's ~/.ssh. Roster
carries per-node accounts (Rendering.Accounts). Tested, including ssh-client
composed end-to-end. Not deployed.
14 lines
979 B
SQL
14 lines
979 B
SQL
-- A node has an operator account: the human login on it (novox/hq to-be 29).
|
|
--
|
|
-- The mesh modelled the machine but not the person on it — `jochens` on novox, `ace` on ace,
|
|
-- `jochen` on shanks and g14. That name decides who a file under a home is owned by and which
|
|
-- account `ssh <node>` logs in as; it was silently lost when the predecessor's per-node `user:`
|
|
-- was not carried over, and `ssh ace` failed to `ace` because nothing here said so.
|
|
--
|
|
-- Empty rather than null and defaulted, because "no operator account known yet" is a real state
|
|
-- (a freshly enrolled machine, a headless box). The home is stored too rather than always assumed
|
|
-- to be /home/<account>, because root's is /root and a machine may put a home elsewhere; empty
|
|
-- means "derive it" (/root for root, /home/<account> otherwise), so the common case needs no entry.
|
|
alter table node add column account text not null default '';
|
|
alter table node add column account_home text not null default '';
|