jschoubben
e0bf87c2e3
mesh/repo-check head e0bf87c2e3da merged into trunk ef1e98f8678c — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
mesh/merge-gate head e0bf87c2e3da merged into trunk ef1e98f8678c — pass: group fix/1873-system-state-dirs composed: every machine composes with the change …
mesh/check failed: unit: i3/cmd/i3-tools.TestTheMainFileAndEveryModulesContributionLoadTogether: manifest_test.go:247: expected the launcher, clipboar…
mesh/delivery delivered
mesh/delivery-group group fix/1873-system-state-dirs delivered: every member is delivered
The systemd and postgres modules' state directories said place ".", which is /var/lib/systemd and /var/lib/postgres: directories the systemd and postgresql packages own (root 0755; postgres 0700). The node-engine took both before issue 339's rule and gave them to the operator's account, 0700, on every machine; postgres's grants directory, placed by default, lay inside /var/lib/postgres too. What each module keeps moves to a directory of its own, "data", placed "mesh" (/var/lib/mesh/systemd, /var/lib/mesh/postgres): the unlink record, and postgres's own secrets (the same values: the vault keys them by name), consumers.json and grants. The store's data stays /var/lib/mesh-store, untouched. The node-engine keeps no found owner or mode for a directory, and forgets one no longer declared as it stands; it sets the declared owner and mode on a directory it recorded at the same path under the same id. So for this delivery "state" names the package's directory with the package's owner and mode, and the engine gives it back; the next change drops "state". The postgres container is recreated, its secret's volume moving. checks/owned/system-known keeps systemd state and postgres state, declared for this delivery only; postgres's consumers and grants leave the list.