A take acts on the preview it showed; a setting is judged where it is stored; a kept network and a minted secret are said (hq ADR 0163) #206

2026-10-01T21:47:51Z

mesh-admin commented

2026-10-01 21:47:51 +00:00

The controller's half of what ADR 0163 left after 201–205. Merge mesh-host 64 first and let it roll on every machine: this controller sends networks and left_out in a declaration only when a setting or a left-out module calls for them, and an older host refuses a field it does not know.

Rule 1. take ends its preview with a digest; take <node> <module> --yes <digest> acts on exactly that preview. A changed preview, or an account of the machine older than the flip allows (15 min), is refused. A module the machine holds nothing for has nothing to compare, and --yes suffices (the API and existing callers keep working). A published port's reach is said as the machine reported it, behind the found firewall whose rules are not read.
Rule 2. Every secret the module holds on the machine is listed with its origin (inventory.SecretsOf). A minted, unaccepted one for a service whose data was found refuses, naming the secret accept that carries the existing value in or --mint <name>.
Rule 4. The per-machine setting networks ({"networks": {"<container id>": ["<found network>"]}}) keeps a found network for a taken container; accepted for an adopted machine only; the container's declaration carries it; the preview names it.
Rule 6 (issue 096). One judgement, catalogue.JudgeSettings, run by SetSettings before storing and by Compose: settings set refuses by node, module, layer and key what cannot compose or reaches nothing; a definition that moved under a stored setting leaves that module out (Composed.LeftOut, envelope left_out), plan and push say it by name, and the machine is told everything else. The old whole-machine refusal for a stray setting is gone; plan prints a stray setting as a note. Rules and renderingFor skip a left-out module too.

make check green (19 packages, store-backed tests included). Fixtures that stored settings against modules with nothing to compose them were given the resources they implied.

The controller's half of what ADR 0163 left after 201–205. **Merge mesh-host 64 first and let it roll on every machine**: this controller sends `networks` and `left_out` in a declaration only when a setting or a left-out module calls for them, and an older host refuses a field it does not know. - **Rule 1.** `take` ends its preview with a digest; `take <node> <module> --yes <digest>` acts on exactly that preview. A changed preview, or an account of the machine older than the flip allows (15 min), is refused. A module the machine holds nothing for has nothing to compare, and `--yes` suffices (the API and existing callers keep working). A published port's reach is said as the machine reported it, behind the found firewall whose rules are not read. - **Rule 2.** Every secret the module holds on the machine is listed with its origin (`inventory.SecretsOf`). A minted, unaccepted one for a service whose data was found refuses, naming the `secret accept` that carries the existing value in or `--mint <name>`. - **Rule 4.** The per-machine setting `networks` (`{"networks": {"<container id>": ["<found network>"]}}`) keeps a found network for a taken container; accepted for an adopted machine only; the container's declaration carries it; the preview names it. - **Rule 6 (issue 096).** One judgement, `catalogue.JudgeSettings`, run by `SetSettings` before storing and by `Compose`: `settings set` refuses by node, module, layer and key what cannot compose or reaches nothing; a definition that moved under a stored setting leaves that module out (`Composed.LeftOut`, envelope `left_out`), `plan` and `push` say it by name, and the machine is told everything else. The old whole-machine refusal for a stray setting is gone; `plan` prints a stray setting as a note. `Rules` and `renderingFor` skip a left-out module too. `make check` green (19 packages, store-backed tests included). Fixtures that stored settings against modules with nothing to compose them were given the resources they implied.

jschoubben force-pushed feat/a-take-is-a-comparison-the-rest from 934c736fcf to 420a85855d

2026-10-02 00:31:15 +00:00

Compare

jschoubben added 1 commit 2026-10-02 09:04:00 +00:00

A take acts on the preview it showed; a setting is judged where it is stored; a kept network and a minted secret are said (hq ADR 0163) fbc3d320ea

take ends its preview with a digest and --yes names it, as the flip does; a
changed preview or an account older than the flip allows is refused. A module
the machine holds nothing for has nothing to compare, and --yes suffices. A
published port's reach is said as the machine reported it. Every secret the
module holds on the machine is listed with where it came from, and one the
mesh minted for a service whose data was found refuses unless --mint names it.

One judgement of a module's settings against its definition, in the catalogue:
settings set refuses what cannot compose or reaches nothing, naming node,
module, layer and key; Compose leaves out a module whose definition moved
under a stored setting, the envelope says so (left_out), plan and push say it
by name, and the machine is told everything else. A stray setting no longer
refuses the whole machine where it is read (issue 096).

The per-machine setting networks keeps a found network for a taken container,
on an adopted machine only; the container's declaration carries it and the
preview names it (rule 4).

jschoubben force-pushed feat/a-take-is-a-comparison-the-rest from 420a85855d to fbc3d320ea

2026-10-02 09:04:00 +00:00

Compare

mesh-admin merged commit 0c003774ba into main

2026-10-02 09:04:05 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#206