3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	dc62fd0075	Let a shell parameter operator after a known word pass, so ${PORT:-8080} is not refused (issue 231) ... The case-insensitive rule for the mesh's namespace words took ${PORT:-8080}, ${SHELL:-/bin/sh}, ${SECRET:?unset} and ${dir:-/tmp} for misspellings, though they are among the commonest lines of a script or env file. A :-, :=, :+ or :? after the colon is the shell's, whatever the word's case.	2026-10-11 02:20:43 +02:00
jschoubben	525b2c1a11	Sweep the definition, not the filled values, and judge each field alike at check and composition (issue 231) ... The first sweep ran at composition over the resource after settings, bindings and machine facts were filled, so an operator's value such as ${labels:instance} was refused as a misspelling its author never wrote, and the whole machine got nothing. Both points now sweep the resource as the manifest wrote it, against one table of which fields each pass fills, so the check and composition refuse the same things. Any ${<known namespace>: its pattern does not take is refused whatever its case or key. Issue 231's undeclared-setting half is not met here: refusing a key the module does not declare (ADR 0164) is not built and is handed to issue 398.	2026-10-11 02:15:37 +02:00
jschoubben	360c318e85	Refuse a placeholder no pass consumes, so a misspelling never reaches a machine as text (issue 231)	2026-10-11 02:06:14 +02:00