Policy helper output can merge into a source's settings, so a failure costs less.
What's wrong with this entry?
An entry in an enterprise policy helper can declare how its produced managed settings combine with the settings of the source that delivered it: replace, the default and current behaviour, or merge, a deep merge over that source's own settings. Under merge a helper that fails costs only the keys it would have contributed, rather than the whole policy.
- Under merge, helper keys win and arrays replace rather than concatenate.
- Helper validation now also records the script's size and a flag for whether the entry merges its output.
- Status notices include non-status errors when the helper merges.
"How the helper's managedSettings compose with the settings of the source that delivered this entry: 'replace' (default) — the output is the policy; 'merge' — the output is deep-merged over that source's own settings (helper keys win, arrays replace), so a failed helper costs only the delta"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.