From 9727c320342dfaffeb13c4b5894fb4a9047943d7 Mon Sep 17 00:00:00 2001 From: liamfallon Date: Tue, 19 Mar 2019 16:29:56 +0000 Subject: Move examples into separate module Issue-ID: POLICY-1195 Change-Id: Id2dc5b5b490134648ca267e27b795f3f4c03bc7b Signed-off-by: liamfallon --- .../src/test/resources/policies/README.txt | 25 ---------------------- 1 file changed, 25 deletions(-) delete mode 100644 models-tosca/src/test/resources/policies/README.txt (limited to 'models-tosca/src/test/resources/policies/README.txt') diff --git a/models-tosca/src/test/resources/policies/README.txt b/models-tosca/src/test/resources/policies/README.txt deleted file mode 100644 index 942913d5c..000000000 --- a/models-tosca/src/test/resources/policies/README.txt +++ /dev/null @@ -1,25 +0,0 @@ -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 -- cgit 1.2.3-korg