Merge "Document the error code on conditional update/delete"
This commit is contained in:
@@ -270,7 +270,7 @@ associates a port with or disassociates a port from a floating IP.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 404, 409
|
||||
Error response codes: 400, 401, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -332,7 +332,7 @@ This example deletes a floating IP:
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404
|
||||
Error response codes: 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -429,6 +429,9 @@ the client.
|
||||
| | IP allocated on subnet |
|
||||
| | Conflicting IP allocation pools for subnet |
|
||||
+-------+--------------------------------------------------------------+
|
||||
|``412``| Precondition failed |
|
||||
| | The revision number is mismatched |
|
||||
+-------+--------------------------------------------------------------+
|
||||
|``500``| Internal server error |
|
||||
| | Internal OpenStack Networking error |
|
||||
+-------+--------------------------------------------------------------+
|
||||
@@ -459,3 +462,9 @@ In addition, the ``If-Match constraints based on revision_number`` extension
|
||||
(``revision-if-match``) allows API consumers to leverage the ``If-Match`` HTTP
|
||||
header to conditionally update/delete a resource when the HTTP ``If-Match``
|
||||
header matches the ``revision_number`` of the said resource.
|
||||
|
||||
If the HTTP ``If-Match`` header doesn't match the ``revision_number`` of the
|
||||
resource, users will receive the following errors:
|
||||
|
||||
- ``412 Precondition failed`` - Update/Delete the target resource has been
|
||||
denied due to the mismatch of revision number.
|
||||
|
@@ -176,7 +176,7 @@ Updates a log resource.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 404
|
||||
Error response codes: 400, 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -228,7 +228,7 @@ Deletes a log resource.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 400, 401, 404
|
||||
Error response codes: 400, 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -186,7 +186,7 @@ Updates a network.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 403, 404
|
||||
Error response codes: 400, 401, 403, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -277,7 +277,7 @@ Deletes a network and its associated resources.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404, 409
|
||||
Error response codes: 401, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -191,7 +191,7 @@ Only admins and users with a specific role can update the data plane status
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 403, 404, 409
|
||||
Error response codes: 400, 401, 403, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -290,7 +290,7 @@ the respective subnets allocation pools.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 403, 404
|
||||
Error response codes: 401, 403, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -260,7 +260,7 @@ response code.
|
||||
|
||||
Normal response codes: 202
|
||||
|
||||
Error response codes: 400, 401, 404
|
||||
Error response codes: 400, 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -311,7 +311,7 @@ Deletes a QoS policy.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 400, 401, 404
|
||||
Error response codes: 400, 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -238,7 +238,7 @@ remove router interface operations.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 404
|
||||
Error response codes: 400, 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -307,7 +307,7 @@ interfaces before you delete the router.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404, 409
|
||||
Error response codes: 401, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -178,7 +178,7 @@ Deletes a rule from an OpenStack Networking security group.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404
|
||||
Error response codes: 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -162,7 +162,7 @@ Updates a security group.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 403, 404
|
||||
Error response codes: 400, 401, 403, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -217,7 +217,7 @@ not return a response body.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404, 409
|
||||
Error response codes: 401, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -60,7 +60,7 @@ Updates a segment.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 403, 404
|
||||
Error response codes: 400, 401, 403, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -106,7 +106,7 @@ Deletes a segment and its associated resources.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404, 409
|
||||
Error response codes: 401, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -70,7 +70,7 @@ Updates a subnet pool.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 403, 404
|
||||
Error response codes: 400, 401, 403, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -138,7 +138,7 @@ are still in use.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404
|
||||
Error response codes: 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -348,7 +348,7 @@ attributes results in a ``400 Bad Request`` error.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 403, 404
|
||||
Error response codes: 400, 401, 403, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -416,7 +416,7 @@ The operation fails if subnet IP addresses are still allocated.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404
|
||||
Error response codes: 401, 404, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
@@ -282,7 +282,7 @@ that it prevents operations such as as adding/removing subports.
|
||||
|
||||
Normal response codes: 200
|
||||
|
||||
Error response codes: 400, 401, 404, 409
|
||||
Error response codes: 400, 401, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
@@ -384,7 +384,7 @@ Deletes a trunk, if its state allows it.
|
||||
|
||||
Normal response codes: 204
|
||||
|
||||
Error response codes: 401, 404, 409
|
||||
Error response codes: 401, 404, 409, 412
|
||||
|
||||
Request
|
||||
-------
|
||||
|
Reference in New Issue
Block a user