Add test policytype and policies

Some example policies for vDNS, vFW and vCPE use
cases using DCAE TCA.

The .input are the expected REST body from the
calling client (eg. CLAMP).

While the .output are the expected REST body for the return
response from policy.

The .tosca.yaml are what the DBAO will look like internally.

Upgraded to support policy/model merge.

Fixed missing tca_policy field in monitoring policies.

Update for policy-id.

Issue-ID: POLICY-1273
Change-Id: Ib087b184c3ac9a058fe600c6c8a28cca3a71fbea
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>

1 files changed, 25 insertions, 0 deletions

diff --git a/main/src/test/resources/policies/README.txt b/main/src/test/resources/policies/README.txt
new file mode 100644
index 00000000..942913d5
--- /dev/null
+++ b/main/src/test/resources/policies/README.txt
@@ -0,0 +1,25 @@
+The "input" prefix indicates that this is what the payload looks like on the POST. While the "output" prefix
+indicates that this is what the payload looks like when the response goes back to the caller.
+
+For each of the use cases, there is at least one configuration policy for DCAE Microservice. 
+
+*.monitoring.input.[json|yaml] <-- POST request
+
+*.monitoring.output.[json|yaml] --> POST response
+
+The Operational Policies:
+
+*.operational.input.yaml --> Can Pam change this to JSON??
+
+*.operational.output.json --> POST response
+
+The Guard Policies:
+
+*.guard.[frequency|minmax].json <-- POST request
+
+*.guard.[frequency|minmax].json --> POST response
+
+For DBAO, the following are internal TOSCA Representations for the Operational and Guard policies, with the
+contents of the yaml or JSON URL Encoded:
+
+*.output.tosca.yaml