Inconsistent use of parameters when using policy to set categories

Description

When using this to set policies it works.

<policy name="Set category - Nodes" class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy">
<parameter key="category" value="Nodes"/>
<parameter key="matchBehavior" value="ALL_PARAMETERS"/>
</policy>
<policy name="Set category - Network" class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy">
<parameter key="category" value="Network"/>
<parameter key="matchBehavior" value="ALL_PARAMETERS"/>
</policy>

When using this it does not work:

<policy name="Set category - Nodes" class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy">
<parameter key="category" value="Nodes"/>
<parameter key="matchBehavior" value="ANY_PARAMETERS"/>
</policy>
<policy name="Set category - Network" class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy">
<parameter key="category" value="Network"/>
<parameter key="matchBehavior" value="ANY_PARAMETERS"/>
</policy>

It seems to be backwards that labels get applied when "ALL_PARAMETERS" is matched and no actual paramters present, but ANY_PARAMETERS won't match with no paramters present.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created April 17, 2014 at 12:16 AM
Updated September 21, 2021 at 6:24 PM