1 tosca_definitions_version: tosca_simple_yaml_1_1_0
4 derived_from: tosca.policies.Root
13 onap.policies.base.Middle:
14 derived_from: onap.policies.Base
24 onap.policies.base.middle.Test:
25 derived_from: onap.policies.base.Middle
55 nonmatchableTimestamp:
61 nonmatchableListInteger:
68 Every entry in the list is matchable, the attribute id will be the same for all value. eg. the
77 Every entry in the map is matchable, however the attribute id will be set by the key.
82 nonmatchableMapString:
85 Nothing gets matched - however you have no control over the LHS key. Someone could
86 easily set that value to a matchable property name defined elsewhere.
91 description: we can only ignore this - should get caught in the API
93 type: onap.datatype.zero
95 The matchable field in a datatype must be IGNORED, because this will result in too many assumptions
96 as we may go down many levels of datatypes, lists of datatypes, maps of datatypes, etc. Does every
97 field in the datatype become matchable? That does not make sense right now to write a Policy Type
103 derived_from: tosca.datatypes.Root
104 description: Note that we do not have to declare matchable for each property.
110 zeroBooleanMatchable:
118 zeroIntegerMatchable:
122 zeroTimestampMatchable:
127 type: onap.datatype.one
130 description: we can only ignore this - should get caught in the API
132 type: another.missing.datatype
134 derived_from: tosca.datatypes.Root
142 propertyTwoListOfDatatype:
145 type: onap.datatype.two
147 derived_from: tosca.datatypes.Root
159 propertyThreeDatatype:
162 type: onap.datatype.three
164 derived_from: tosca.datatypes.Root
166 threeStringMatchable:
170 threeIntegerMatchable: