Skip to content

GitLab

Commit 56412743 authored by moscatelli's avatar moscatelli
Browse files

SOL003_118/SOL003_119/SOL003_120: Individual PM job POST and GET description fields updated

parent c47c0e29
Pipeline #1183 passed with stage
in 0 seconds
Hide whitespace changes
Inline Side-by-side
Showing with 27 additions and 12 deletions
src/SOL003/VNFPerformanceManagement/VNFPerformanceManagement.yaml
View file @ 56412743
......@@ -290,7 +290,7 @@ paths:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503"
504:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504"
###############################################################################
# Individual PM job #
###############################################################################
......@@ -302,17 +302,17 @@ paths:
Identifier of the PM job.
This identifier can be retrieved from the resource referenced by the
"Location" HTTP header in the response to a POST request creating a
new PM job resource. It can also be retrieved from the "id"
new "Individual PM job" resource. It can also be retrieved from the "id"
attribute in the payload body of that response.
in: path
type: string
required: true
get:
description: >
Query PM Job
Query PM Job.
The client can use this method for reading an individual PM job.
This method shall follow the provisions specified in the tables 6.4.3.3.2-1 and 6.4.3.3.2-2
for URI query parameters, request and response data structures, and response codes.
parameters:
- name: Accept
description: >
......@@ -339,9 +339,9 @@ paths:
description: >
200 OK
Information about an individual PM job was queried successfully.
The response body shall contain a representation of the PM job
resource.
Shall be returned when information about an individual PM job has been read successfully.
The response body shall contain a representation of the "Individual PM job" resource,
as defined in clause 6.5.2.7.
headers:
Content-Type:
description: >
......@@ -372,20 +372,28 @@ paths:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401"
403:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403"
404:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
405:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"
406:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406"
422:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422"
500:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500"
503:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503"
504:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504"
delete:
description: >
Delete PM Job
Delete PM Job.
This method terminates an individual PM job.
This method shall follow the provisions specified in the tables 6.4.3.3.5-1 and 6.4.3.3.5-2
for URI query parameters, request and response data structures, and response codes.
As the result of successfully executing this method, the "Individual PM job" resource shall not exist any longer.
parameters:
- name: Authorization
description: >
......@@ -405,7 +413,7 @@ paths:
description: >
204 NO CONTENT
The PM job was deleted successfully.
Shall be returned when the PM job has been deleted successfully.
The response body shall be empty.
headers:
WWW-Authenticate:
......@@ -428,14 +436,21 @@ paths:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/401"
403:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/403"
404:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/404"
405:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/405"
406:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/406"
422:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/422"
500:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/500"
503:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/503"
504:
$ref: "../../responses/SOL002SOL003_resp.yaml#/responses/504"
###############################################################################
# Individual performance report #
###############################################################################
......
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