Commit 8dbd8c90 authored by Sana Zulfiqar's avatar Sana Zulfiqar
Browse files

added error codes

parent ee03dbc6
Pipeline #7771 passed with stage
in 0 seconds
......@@ -48,28 +48,28 @@ paths:
$ref: '#/components/responses/Coordination.Post.201'
"202":
$ref: '#/components/responses/Coordination_async.Post.202'
"403":
$ref: '#/components/responses/Coordination.Post.403'
"409":
$ref: '#/components/responses/Coordination.Post.409'
"503":
$ref: '#/components/responses/Coordination.Post.503'
"400":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/400
"401":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/401
"403":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/403
"404":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/404
"405":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/405
"406":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/406
"409":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/409
"422":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/422
"429":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/429
"500":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/500
"503":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/503
"504":
$ref: ../../responses/SOL002SOL003_resp.yaml#/components/responses/504
......@@ -272,6 +272,123 @@ components:
format: url
content: {}
Coordination.Post.403:
description: >
403 FORBIDDEN
Shall be returned upon the following error: The starting of the coordination operation has been
rejected.
No "individual coordination action" resource shall be created.
A ProblemDetails structure shall be included in the response to provide more details about the rejection
in the "details" attribute.
headers:
Content-Type:
description: The MIME type of the body of the response.
schema:
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
schema:
type: string
maximum: 1
minimum: 0
Version:
description: >
Version of the API used in the response.
schema:
type: string
maximum: 1
minimum: 1
content:
application/json:
schema:
$ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
Coordination.Post.409:
description: >
409 CONFLICT
Shall be returned upon the following error: The operation cannot be executed currently, due to a
conflict with the state of the "Coordinations" resource.
Typically, this is due to the fact that no more coordination actions can be executed currently e.g.
because too many of them, or conflicting ones, are in progress.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute should
convey more information about the error.
headers:
Content-Type:
description: The MIME type of the body of the response.
schema:
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
schema:
type: string
maximum: 1
minimum: 0
Version:
description: >
Version of the API used in the response.
schema:
type: string
maximum: 1
minimum: 1
content:
application/json:
schema:
$ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
Coordination.Post.503:
description: >
503 SERVICE UNAVAILABLE
Shall be returned upon the following error: The API producer has chosen the synchronous mode and
cannot perform the requested coordination currently, but expects to be able to perform it sometime
in the future.
No "individual coordination action" resource shall be created.
A ProblemDetails structure shall be included in the response to provide more details about the
rejection in the "details" attribute.
The HTTP response shall include a "Retry-After" HTTP header that indicates the delay after
which it is suggested to repeat the coordination request with the same set of parameters. The VNFM
shall record the signalled delay value in the "delay" attribute of the applicable entry in the
"rejectedLcmCoordinations" array in the "VnfLcmOpOcc" structure.
headers:
Content-Type:
description: The MIME type of the body of the response.
schema:
type: string
maximum: 1
minimum: 1
WWW-Authenticate:
description: >
Challenge if the corresponding HTTP request has not provided
authorization, or error details if the corresponding HTTP
request has provided an invalid authorization token.
schema:
type: string
maximum: 1
minimum: 0
Version:
description: >
Version of the API used in the response.
schema:
type: string
maximum: 1
minimum: 1
content:
application/json:
schema:
$ref: "../../definitions/SOL002SOL003_def.yaml#/definitions/ProblemDetails"
LcmCoord.Get.200:
description: |
200 OK
......
Supports Markdown
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