Passing taskParameters from ApexConfig to policy logic

TaskParameters can be used to pass parameters from ApexConfig to the policy logic. In the config, these are optional.
Usage as below:

{
  "engineParameters": {
    "taskParameters": [
      {
        "key": "ParameterKey1",
        "value": "ParameterValue1"
      },
      {
        "taskId": "TaskIdVal",
        "key": "ParameterKey2",
        "value": "ParameterValue2"
      }
    ]
  }
}

In the taskLogic, taskParameters can be accessed as below:
	eg:  executor.parameters.get("ParameterKey1"))

If taskId is provided in ApexConfig for an entry, then that
parameter is updated only for that particular task. Otherwise, the task
parameter is added to all tasks.

Change-Id: I9e1b3d3697428309e7d86db40b63ffe822935b69
Issue-ID: POLICY-2364
Signed-off-by: a.sreekumar <ajith.sreekumar@est.tech>
10 files changed
tree: 6ed8b1ebb110992c5e7985100478ab5b216d185d
  1. auth/
  2. client/
  3. context/
  4. core/
  5. examples/
  6. model/
  7. packages/
  8. plugins/
  9. releases/
  10. services/
  11. src/
  12. testsuites/
  13. tools/
  14. .gitignore
  15. .gitreview
  16. BUILD.adoc
  17. docker_build.sh
  18. docker_merge.sh
  19. docker_verify.sh
  20. INFO.yaml
  21. LICENSE.txt
  22. pom.xml
  23. README.md
  24. version.properties
README.md

Copyright (C) 2016-2018 Ericsson. 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 APEX PDP Engine code. The settings file only needs to support the standard Maven repositories (e.g. central = http://repo1.maven.org/maven2/), and any proxy settings needed in your environment.

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