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
5 files changed
tree: 5b2fd019981e41843bb633e5450f8b687abf12bc
  1. models-base/
  2. models-dao/
  3. models-decisions/
  4. models-errors/
  5. models-examples/
  6. models-interactions/
  7. models-pap/
  8. models-pdp/
  9. models-provider/
  10. models-sim/
  11. models-tosca/
  12. releases/
  13. .gitignore
  14. .gitreview
  15. INFO.yaml
  16. LICENSE.txt
  17. lombok.config
  18. pom.xml
  19. README.md
  20. version.properties
README.md

Copyright 2018 AT&T Intellectual Property. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy Model code that is agnostic to any PDP. It is common amongst all the repositories.

To build it using Maven 3, run: mvn clean install