A getConfig query with matching attributes does not work for a policy that is modeled using TOSCA. Currently, there is no way a modeler can specify attributes in a TOSCA model against which the policy system can perform matching for a getConfig query.

The solution is to (1) extend the current TOSCA specifications by including either a specific field or an annotation and (2) update the policy search module such that policies are filtered based on the matching attributes specified in a query.

There are two potential options to extend the current TOSCA specs:

 Specific field-based solution:

attribute:
    type: list
    required: True

    matchable: True
    entry_schema:
      type: string
      constraints:
        - valid_values: ["val1", “val2", “val3"] 

Annotation-based solution: 

@matchable

attribute:
    type: list
    required: True
    entry_schema:
      type: string
      constraints:
        - valid_values: ["val1", “val2", “val3"]