Commit 9f5f89cf authored by Samir Medjiah's avatar Samir Medjiah

Correcting typos in some paramters names ("filter", etc.) in NS LCM, NS FM, VNG PM interfaces

parent 929e0ac3
Pipeline #724 failed with stage
in 0 seconds
...@@ -89,10 +89,10 @@ paths: ...@@ -89,10 +89,10 @@ paths:
The client can use this method to retrieve information about the alarm list. The client can use this method to retrieve information about the alarm list.
parameters: parameters:
- name: "filter" - name: filter
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Attribute-based filtering expression according to clause 4.3.2. Attribute-based filtering expression according to clause 4.3.2.
The NFVO shall support receiving this parameter as part of the URI query string. The NFVO shall support receiving this parameter as part of the URI query string.
...@@ -508,10 +508,10 @@ paths: ...@@ -508,10 +508,10 @@ paths:
Table 8.4.4.3.2-1: URI query parameters supported. Table 8.4.4.3.2-1: URI query parameters supported.
parameters: parameters:
- name: "filter" - name: filter
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Attribute-based filtering expression according to clause 4.3.2. Attribute-based filtering expression according to clause 4.3.2.
The NFVO shall support receiving this parameter as part of the URI The NFVO shall support receiving this parameter as part of the URI
......
...@@ -192,41 +192,41 @@ paths: ...@@ -192,41 +192,41 @@ paths:
This method shall support the URI query parameters, request and response data structures, and response codes, as This method shall support the URI query parameters, request and response data structures, and response codes, as
specified in the Tables 6.4.2.3.2-1 and 6.4.2.3.2-2. specified in the Tables 6.4.2.3.2-1 and 6.4.2.3.2-2.
parameters: parameters:
- name: "filter" - name: filter
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
"Attribute-based filtering expression according to clause 4.3.2. Attribute-based filtering expression according to clause 4.3.2.
The NFVO shall support receiving this parameter as part of the URI The NFVO shall support receiving this parameter as part of the URI
query string. The OSS/BSS may supply this parameter. query string. The OSS/BSS may supply this parameter.
All attribute names that appear in the NsInstance and in data types All attribute names that appear in the NsInstance and in data types
referenced from it shall be supported by the NFVO in the filter expression." referenced from it shall be supported by the NFVO in the filter expression.
- name: "all_fields" - name: all_fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
"Include all complex attributes in the response. See clause 4.3.3 for details. Include all complex attributes in the response. See clause 4.3.3 for details.
The NFVO shall support this parameter." The NFVO shall support this parameter.
- name: "fields" - name: fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
"Complex attributes to be included into the response. See clause 4.3.3 for "Complex attributes to be included into the response. See clause 4.3.3 for
details. The NFVO should support this parameter." details. The NFVO should support this parameter."
- name: "exclude_fields" - name: exclude_fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
"Complex attributes to be excluded from the response. See clause 4.3.3 for "Complex attributes to be excluded from the response. See clause 4.3.3 for
details. The NFVO should support this parameter." details. The NFVO should support this parameter."
- name: "exclude_default" - name: exclude_default
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
"Indicates to exclude the following complex attributes from the response. "Indicates to exclude the following complex attributes from the response.
See clause 4.3.3 for details. The NFVO shall support this parameter. See clause 4.3.3 for details. The NFVO shall support this parameter.
...@@ -912,34 +912,34 @@ paths: ...@@ -912,34 +912,34 @@ paths:
This method shall follow the provisions specified in the Tables 6.4.9.3.2-1 and 6.4.9.3.2-2 for URI query parameters, This method shall follow the provisions specified in the Tables 6.4.9.3.2-1 and 6.4.9.3.2-2 for URI query parameters,
request and response data structures, and response codes. request and response data structures, and response codes.
parameters: parameters:
- name: "filter" - name: filter
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Attribute-based filtering expression according to clause 4.3.2. Attribute-based filtering expression according to clause 4.3.2.
The NFVO shall support receiving this parameter as part of the URI query string. The NFVO shall support receiving this parameter as part of the URI query string.
The OSS/BSS may supply this parameter. The OSS/BSS may supply this parameter.
All attribute names that appear in the NsLcmOpOcc and in data types referenced All attribute names that appear in the NsLcmOpOcc and in data types referenced
from it shall be supported by the NFVO in the filter expression. from it shall be supported by the NFVO in the filter expression.
- name: "fields" - name: fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Complex attributes to be included into the response. See clause 4.3.3 for details. The Complex attributes to be included into the response. See clause 4.3.3 for details. The
NFVO should support this parameter. NFVO should support this parameter.
- name: "exclude_fields" - name: exclude_fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Complex attributes to be excluded from the response. See clause 4.3.3 for details. Complex attributes to be excluded from the response. See clause 4.3.3 for details.
The NFVO should support this parameter. The NFVO should support this parameter.
- name: "exclude_default" - name: exclude_default
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Indicates to exclude the following complex attributes from the response. See Indicates to exclude the following complex attributes from the response. See
clause 4.3.3 for details. The NFVO shall support this parameter. clause 4.3.3 for details. The NFVO shall support this parameter.
......
...@@ -90,41 +90,41 @@ paths: ...@@ -90,41 +90,41 @@ paths:
Tables 9.4.2.3.2-1 and 9.4.2.3.2-2 for URI query parameters, Tables 9.4.2.3.2-1 and 9.4.2.3.2-2 for URI query parameters,
request and response data structures, and response codes. request and response data structures, and response codes.
parameters: parameters:
- name: "filter" - name: filter
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Attribute-based filtering expression according to clause 4.3.2. Attribute-based filtering expression according to clause 4.3.2.
The NFVO shall support receiving this parameter as part of the URI query string. The The NFVO shall support receiving this parameter as part of the URI query string. The
OSS/BSS may supply this parameter. OSS/BSS may supply this parameter.
All attribute names that appear in the VnfPkgInfo and in data types referenced from it shall All attribute names that appear in the VnfPkgInfo and in data types referenced from it shall
be supported by the NFVO in the filter expression. be supported by the NFVO in the filter expression.
- name: "all_fields" - name: all_fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Include all complex attributes in the response. See clause 4.3.3 for details. The NFVO Include all complex attributes in the response. See clause 4.3.3 for details. The NFVO
shall support this parameter. shall support this parameter.
- name: "fields" - name: fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Complex attributes to be included into the response. See clause 4.3.3 for details. The Complex attributes to be included into the response. See clause 4.3.3 for details. The
NFVO should support this parameter. NFVO should support this parameter.
- name: "exclude_fields" - name: exclude_fields
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Complex attributes to be excluded from the response. See clause 4.3.3 for details. The Complex attributes to be excluded from the response. See clause 4.3.3 for details. The
NFVO should support this parameter. NFVO should support this parameter.
- name: "exclude_default" - name: exclude_default
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Indicates to exclude the following complex attributes from the response. See clause 4.3.3 Indicates to exclude the following complex attributes from the response. See clause 4.3.3
for details. for details.
...@@ -1193,10 +1193,10 @@ paths: ...@@ -1193,10 +1193,10 @@ paths:
Tables 9.4.7.8.2-1 and 9.4.8.3.2-2 for URI query parameters, Tables 9.4.7.8.2-1 and 9.4.8.3.2-2 for URI query parameters,
request and response data structures, and response codes. request and response data structures, and response codes.
parameters: parameters:
- name: "filter" - name: filter
in: "query" in: query
required: false required: false
type: "string" type: string
description: > description: >
Attribute-based filtering expression according to clause 4.3.2. Attribute-based filtering expression according to clause 4.3.2.
The NFVO shall support receiving this filtering parameter as part of the URI query The NFVO shall support receiving this filtering parameter as part of the URI query
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment