HorizonRulePolicy - NetSapiens API v2

Analysis rule policy, keyed by rule id, always reported RESOLVED — every rule with its effective mode, severity and bucket severities — rather than as the sparse set of overrides that is stored. An operator deciding whether to promote a rule out of monitor needs to see what is actually in force, and a sparse object makes them reconstruct that from code they cannot read.

On write, send only the rules you are changing; {} for a rule removes its override.

{ "property1": { "mode": "enforce", "severity": "reject", "buckets": { "vendored": "reject", "build-injected": "reject" } }, "property2": { "mode": "enforce", "severity": "reject", "buckets": { "vendored": "reject", "build-injected": "reject" } } }