SOL002_25: filters implemented for VNF LCM operation occurrences GET

src/SOL002/VNFLifecycleManagement/VNFLifecycleManagement.yaml

@@ -21,7 +21,7 @@ externalDocs:
   description: ETSI GS NFV-SOL 002 V2.4.1
   url: http://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/02.04.01_60/gs_NFV-SOL002v020401p.pdf
 
-basePath: /vnfconfig/v1
+basePath: /vnflcm/v1
 
 schemes: 
   - http
@@ -808,6 +808,83 @@ paths:
       description: >
         The client can use this method to query status information about
         multiple VNF lifecycle management operation occurrences.
+      parameters:
+        - name: filter
+          description: >
+            Attribute-based filtering expression according to clause 4.3.2.
+            The VNFM shall support receiving this parameter as part of the URI query string.
+            The EM/VNF may supply this parameter. All attribute names that appear in the VnfLcmOpOcc
+            and in data types referenced from it shall be supported by the VNFM in the filter expression.
+
+            EXAMPLE
+            objects
+            obj1: {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]}
+            obj2: {"id":456, "weight":500, "parts":[{"id":3, "color":"green"}, {"id":4, "color":"blue"}]}
+
+            Request 1:
+            GET …/container
+
+            Response 1:
+            [
+                {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]},
+                {"id":456, "weight":500, "parts":[{"id":3, "color":"green"}, {"id":4, "color":"blue"}]}
+            ]
+
+            Request 2:
+            GET …/container?filter=(eq.weight,100)
+
+            Response 2:
+            [
+                {"id":123, "weight":100, "parts":[{"id":1, "color":"red"}, {"id":2, "color":"green"}]}
+            ]
+          #Request 2 in EXAMPLE from clause 4.3.2 probably wrong, since "," should be used after opOne (eq), "." is used
+          in: query
+          required: false
+          type: string
+        - name: all_fields
+          description: >
+            Include all complex attributes in the response.
+            See clause 4.3.3 for details. The VNFM shall support this parameter.
+          in: query
+          required: false
+          type: string
+        - name: fields
+          description: >
+            Complex attributes to be included into the response.
+            See clause 4.3.3 for details. The VNFM should support this parameter.
+          in: query
+          required: false
+          type: string
+        - name: exclude_fields
+          description: >
+            Complex attributes to be excluded from the response.
+            See clause 4.3.3 for details. The VNFM should support this parameter.
+          in: query
+          required: false
+          type: string
+        - name: exclude_default
+          description: >
+            Indicates to exclude the following complex attributes from the response.
+            See clause 4.3.3 for details. The VNFM shall support this parameter.
+            The following attributes shall be excluded from the VnfLcmOpOcc structure
+            in the response body if this parameter is provided, or none of the parameters
+            "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
+            -	operationParams
+            -	error
+            -	resourceChanges
+            -	changedInfo
+            -	changedExtConnectivity
+          in: query
+          required: false
+          type: string
+        - name: nextpage_opaque_marker
+          description: >
+            Marker to obtain the next page of a paged response.
+            Shall be supported by the VNFM if the VNFM supports alternative 2
+            (paging) according to clause 4.7.2.1 for this resource.
+          in: query
+          required: false
+          type: string
       responses:
         200:
           description: >