Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
NFV - Network Functions Virtualisation
SOL002-SOL003
Commits
86c33a5f
Commit
86c33a5f
authored
Jul 17, 2019
by
Samir Medjiah
Browse files
SOL002_125 PATCH Method (on "Alarm") response updated
parent
a2558e1e
Changes
1
Hide whitespace changes
Inline
Side-by-side
src/SOL002/VNFFaultManagement/VNFFaultManagement.yaml
View file @
86c33a5f
...
...
@@ -318,9 +318,9 @@ paths:
description
:
>
200 OK
T
he request was accepted and completed.
The response body shall
contain attribute modifications for
an ‘Individual alarm’
resource.
Shall be returned when t
he request was accepted and completed.
The response body shall
contain attribute modifications for
an "Individual alarm"
resource.
headers
:
Content-Type
:
description
:
The MIME type of the body of the response.
...
...
@@ -358,14 +358,24 @@ paths:
description
:
>
409 CONFLICT
Error: The operation cannot be executed currently, due to a conflict with the state of
the "Individual alarm" resource.
Typically, this is due to the fact that the alarm is already in the state that is requested
to be set (such as trying to acknowledge an already-acknowledged alarm).
The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall
convey more information about the error.
Shall be returned upon the following error: The operation cannot be executed
currently, due to a conflict with the state of the "Individual alarm" resource.
Typically, this is due to the fact that the alarm is already in the state that
is requested to be set (such as trying to acknowledge an already-acknowledged
alarm).
The response body shall contain a ProblemDetails structure, in which the
"detail" attribute shall convey more information about the error.
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/409"
412
:
description
:
>
412 PRECONDITION FAILED
ErrorShall be returned upon the following error: A precondition given in an
HTTP request header is not fulfilled.
Typically, this is due to an ETag mismatch, indicating that the resource was
modified by another entity.
The response body should contain a ProblemDetails structure, in which the
"detail" attribute should convey more information about the error.
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/412"
416
:
$ref
:
"
../../responses/SOL002SOL003_resp.yaml#/responses/416"
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment