openstack/keystone
Code Issues Proposed changes

Fix description for 204 response

Browse Source 
In addition to DELETE requests, keystone may return an HTTP 204 as a
success code for PUT[1] and HEAD[2] requests. It would be quite
disconcerting if keystone were actually deleting resources during such
additive and read-only operations, so this patch simplifies the 204
description so that it is truthful in all of its use cases.

[1] https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=assign-role-to-group-on-domain-detail#assign-role-to-group-on-domain
[2] https://developer.openstack.org/api-ref/identity/v3/index.html?expanded=check-whether-user-belongs-to-group-detail#check-whether-user-belongs-to-group

Change-Id: I0e4f9df873a831d7329e71b77818bc47d3c2bbb2
This commit is contained in:
Colleen Murphy 2017-03-14 00:49:45 +01:00
parent 8ff15d3e0f
commit 37185428dd
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-ref/source/v3/status.yaml
View File

@ -13,7 +13,7 @@
a link to check the progress of the request.
204:
default: |
The server has fulfilled the request by deleting the resource.
The server has fulfilled the request.
300:
default: |
There are multiple choices for resources. The request has to be more