aboutsummaryrefslogtreecommitdiffstats
path: root/main/src/test/resources/policies/README.txt
blob: 942913d5c063bc0a428eda2d798560f82f69dbd5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
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