6 Commits

Include renames

Author	SHA1	Message	Date
jochen	eb5f9d2f53	Allow a setting in a unit's name only as a template's whole instance, never leading with a dash, at most 64 characters ... Third review of mesh-catalog #147. A setting anywhere else in a unit's name could make the unit another unit or another kind; it is now refused where the manifest is read. A value beginning with '-' would be read by systemctl as an option, and a long one is no pool's name.	2026-10-09 01:51:37 +02:00
jochen	e4d2868679	Fill ${setting:} in a service's unit name, and refuse a value that makes no unit name ... A module that holds the distribution's scrub timer for the pool the operator names (zfs-scrub-weekly@<pool>.timer) cannot write the pool into its definition (hq ADR 0112). Settings were substituted only into file content, so the unit reached the machine as "zfs-scrub-weekly@${setting:scrub-pool}.timer", a unit no machine has, and the apply failed far from its cause (second review of mesh-catalog #147). A service's unit now takes ${setting:} from the same layers a file does, and is refused by key when nothing sets it. A value is also refused unless it is only letters, digits, ':', '_', '.' and '-': the name ends up in unit files and systemctl arguments, and a space, a slash or a newline must never reach them. A key a unit asks for is not called stray.	2026-10-09 01:32:32 +02:00
jochen	76babaea52	Read stored manifests leniently and mark the defaults layer (hq ADR 0262 review) ... A strict read of the stored catalogue fails every plan and send once a manifest uses a field an older controller lacks; registration stays strict. A node named default lost its layer to the name check. Judge the operator's keys by whole words, and scan a default under any key.	2026-10-08 17:24:32 +02:00
jochen	e41b78cd77	Fill a preference's ${setting:} from its manifest default (hq ADR 0262) ... Without a default, a running module could never gain a setting: the file asking for it failed to compose until set, and the key was refused as stray until a file asked for it. Defaults sit under the mesh's and the node's settings, never merge into a JSON file, are refused for the operator's own values, and settings shows each value's source.	2026-10-08 17:24:32 +02:00
jschoubben	29be985c23	A served value or a contribution's may be the operator's: ${setting:…} fills there too, refused by name when unset ... Issue 173's rule needs it: a mail provider serves its domain and an identity provider its issuer, and neither is the definition's to state. Declared as ${setting:<key>}, filled from the layers after the overrides; a key so asked for is not stray.	2026-09-30 22:34:43 +02:00
jschoubben	d9dbc9a59a	A definition names no installation: the check, an operator's value, a context on the git seat ... InstallationProblems judges every value the mesh acts on for a name under a public top-level domain or a public address, with prose, the world's registries, resolvers and certificate authorities exempt, and a name a resource means on purpose declared with its reason (names-on-purpose). Run by module check and a catalogue-wide test, not yet at registration, while the declared list shrinks. ${setting:<key>} fills a file from the assignment's settings and is refused when nothing set it. A build context may live on the git seat; the request carries the seat's clone base (novox/hq ADR 0112, ADR 0155, issues 122 and 134).	2026-09-30 18:38:06 +02:00