{"version":"2.1.232","anchor":"managed-policy-cli-documents-are-checked-for-alias-collision","canonical_anchor":"managed-policy-cli-documents-are-checked-for-alias-collision","heading":"Managed policy CLI documents are checked for alias collisions","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/managed-policy-cli-documents-are-checked-for-alias-collision","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Managed policy CLI documents are checked for alias collisions\n\nGateway configs now fail validation if a setting appears under both an alias and its canonical name.\n\n**What**\n\nEach `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.\n\n**Details**\n\n- Previously the alias map was applied with no complaint when both spellings were present, so which one won was not obvious.\n\n**Evidence**\n\n`which are the same setting`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}