Set policyHelpers per platform; WSL falls back to the linux entry, then to the single policyHelper.
What's wrong with this entry?
Administrators can now set a different policy helper executable per platform. policyHelpers is an object keyed by macos, linux, windows and wsl; the entry matching the current platform wins over the existing single policyHelper, and a platform with no entry falls back to policyHelper. A wsl machine with no wsl entry tries the linux entry first.
- Like
policyHelper,policyHelpersis honored only when it arrives from an admin-controlled policy source, not from user or project settings. - Validation is strict: a malformed
policyHelpersfrom an OS-admin policy source is fatal at startup. - If
policyHelpersis configured but has no entry for the current platform and nopolicyHelperis set, a warning is logged and no helper runs.
Per-OS variant of policyHelper, keyed by platform: macos, linux, windows, wsl.
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.232
Warnings when policy helper settings are nested in the wrong place
Both mention policy helper managed
-
v2.1.232
A failing policy helper now falls back to its fixed payload
Both mention policy helper managed
-
v2.1.232
Policy helper executable paths must be in normalized form
Both mention policy helper managed