Commit 69fa1df6 authored by Francesca Moscatelli's avatar Francesca Moscatelli
Browse files

SOL005: Fixed API producer/API consumer

parent 37adea9c
Pipeline #6842 passed with stage
in 0 seconds
......@@ -1664,9 +1664,7 @@ paths:
put:
description: >
The PUT method is used to upload the content of a PNFD archive.
This resource represents the content of the individual PNF descriptor, i.e. PNFD content.
The client can use this resource to upload and download the content of the PNFD.
The PUT method is used to upload the content of a PNFD archive.
parameters:
- name: Accept
description: >
......@@ -2304,15 +2302,8 @@ paths:
get:
description: >
This resource represents an individual subscription.
It can be used by the client to read and to terminate a subscription to
notifications related to NSD management.
The GET method retrieves information about a subscription by reading
an individual subscription resource.
This resource represents an individual subscription.
It can be used by the client to read and to terminate a subscription to
notifications related to NSD management.
The GET method retrieves information about a subscription by reading an individual
subscription resource.
parameters:
- name: Accept
in: header
......@@ -2372,14 +2363,7 @@ paths:
delete:
description: >
This resource represents an individual subscription.
It can be used by the client to read and to terminate a subscription to
notifications related to NSD management.
The DELETE method terminates an individual subscription.
This method shall support the URI query parameters, request and
response data structures, and response codes, as
specified in the Table 5.4.9.3.3-2.
The DELETE method terminates an individual subscription.
parameters:
- name: Authorization
in: header
......
......@@ -105,8 +105,8 @@ paths:
$ref: "../responses/SOL005_resp.yaml#/responses/503"
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by
the API consumer, e.g. during subscription.
The GET method allows the API producer to test the notification endpoint that
is provided by the API consumer, e.g. during subscription.
parameters:
- name: Accept
description: >
......@@ -241,8 +241,8 @@ paths:
$ref: "../responses/SOL005_resp.yaml#/responses/503"
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by
the client, e.g. during subscription.
The GET method allows the API producer to test the notification endpoint that
is provided by the API consumer, e.g. during subscription.
parameters:
- name: Accept
description: >
......@@ -376,8 +376,8 @@ paths:
$ref: "../responses/SOL005_resp.yaml#/responses/503"
get:
description: >
The GET method allows the server to test the notification endpoint that is provided by
the API consumer, e.g. during subscription.
The GET method allows the API producer to test the notification endpoint
that is provided by the API consumer, e.g. during subscription.
parameters:
- name: Accept
description: >
......
......@@ -166,10 +166,9 @@ paths:
'/URI_is_provided_by_the_client_when_creating_the_subscription-VnfPackageChangeNotification':
post:
description: >
The POST method delivers a notification from the server to the client.
This method shall follow the provisions specified in the
Tables 9.4.10.3.1-1 and 9.4.10.3.1-2 for URI query parameters,
request and response data structures, and response codes.
The POST method delivers a notification from the API producer to an API consumer.
The API consumer shall have previously created an "individual subscription resource"
with a matching filter.
parameters:
- name: VnfPackageChangeNotification
description: >
......
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