jschoubben
e8aa7ed9e7
`rollout mint` gives every principal the new bus will have a credential it does not yet have and puts each where its owner reads it: a machine's as a membership — bus address, fingerprint, password, transport — sealed into its declaration (migration 0041, the `bus-membership` resource the host reads after applying); a module's as its broker secret, through the same delivery `module issue` uses; the control plane's own as its `bus` secret. Idempotent, and worked out from where the bus's module is assigned rather than from this process's environment, because this process is still on the old bus when it runs and must be. This is the half of design 28 task 5.2 the first live attempt found missing: a credential was minted only at enrolment, at `module issue` and for a person, so no machine already enrolled could ever be moved. `rollout check` was right to refuse; now there is something to run first.
12 lines
723 B
SQL
12 lines
723 B
SQL
-- A machine already enrolled is moved to the new bus by being told its membership for it
|
|
-- (novox/hq design 28, task 5.2). Until this, a membership — bus address, fingerprint, password,
|
|
-- transport — existed only in the enrolment reply, and nothing could hand one to a machine that
|
|
-- had already joined. The row is the membership sealed to that machine, composed into its
|
|
-- declaration as a file it reads after applying; the plaintext exists once, at minting, and then
|
|
-- only on the machine. One per node: the mesh moves to one bus.
|
|
create table bus_membership (
|
|
node uuid primary key references node(id) on delete cascade,
|
|
sealed text not null,
|
|
since timestamptz not null default now()
|
|
);
|