Add optional controllerName in Op. Legacy Policies 84/103184/3
authorjhh <jorge.hernandez-herrero@att.com>
Thu, 5 Mar 2020 20:32:21 +0000 (14:32 -0600)
committerJorge Hernandez <jorge.hernandez-herrero@att.com>
Mon, 9 Mar 2020 14:55:52 +0000 (14:55 +0000)
commit2bda454c5a0036a8fa5af120a90a0c1f94e76b31
tree5b2fd019981e41843bb633e5450f8b687abf12bc
parent3c1fb89886d7ebf2efe1183e92b4ed8191f506b4
Add optional controllerName in Op. Legacy Policies

Optional controllerName has been added to Legacy Operational
policies to be able to route Operational Policies to an
specific drools controller.

Currently, the policies are deployed to all controllers that
support a policy type.   In the case, that there are multiple
controllers set, and the policy is only to be routed to one of
them, this field should be populated.

Issue-ID: POLICY-2388
Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
Change-Id: I7288ce0069a723b8e6ec535331dc9cda56fbf130
models-examples/src/main/resources/policies/vCPE.policy.operational.legacy.input.json
models-examples/src/main/resources/policies/vCPE.policy.operational.legacy.output.json
models-tosca/src/main/java/org/onap/policy/models/tosca/legacy/concepts/LegacyOperationalPolicy.java
models-tosca/src/main/java/org/onap/policy/models/tosca/legacy/mapping/LegacyOperationalPolicyMapper.java
models-tosca/src/test/java/org/onap/policy/models/tosca/legacy/concepts/LegacyOperationalPolicyTest.java