Gateway configs now fail validation if a setting appears under both an alias and its canonical name.
What's wrong with this entry?
Each managed.policies[].cli document in a gateway config is scanned for a setting written under both an alias and its canonical name. Every collision is a validation error naming both spellings and telling the operator to keep the canonical one.
- Previously the alias map was applied with no complaint when both spellings were present, so which one won was not obvious.
which are the same setting
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Managed-settings review prompt dropped from the main UI
Both mention managed
-
v2.1.242
Startup can wait on a remote managed-settings refresh, with a deadline
Both mention managed
-
v2.1.246
Remote managed settings can defer their consent prompt to the next interactive session
Both mention managed