unknown-env
An advisory by default: it explains, and blocks nothing, on a retired or misspelled MAGUS_* variable handed to a command.
What it catches
A retired or misspelled MAGUS_* variable handed to a command.
Why
A retired or misspelled name is ignored without a word, so the setting the caller meant never takes effect and nothing says so. It fires on the names a command's environment receives: a NAME=value prefix, env NAME=value, env -u NAME, and export. It asks config.EnvVarProblem, the check magus's own startup refuses on (MGS1046), so a name the guard denies is one the binary would refuse, and one it cannot prove wrong passes both.
Default and override
By default this rule takes the decision advise. A workspace sets it by name, in its root
magusfile, to deny, advise or off:
magus\guard.builtins({"unknown-env": "deny"})
A loosening takes effect once it is committed; a tightening applies at once.
Seeing it
A verdict names its rule in brackets, which is how you got here:
advise [unknown-env]: ...
magus describe rule unknown-env prints the same entry at a terminal, and
magus describe rules lists every rule this workspace enforces.
See also
- All rules - what this workspace enforces, deny first
- The guard - how a verdict is reached and wired
- Setting a built-in rule - how a workspace changes this default