trove/api-ref/source
Zhao Chao d597bb4714 Return 204 instead of 200 for root-disable API
As no content will be returned to the client if a root-disable request
succeeds, a HTTP 204 (Not Content) response is more appropriate.

Redis root-disable scenario test fails because it's return HTTP 204, but
all API related tests are expecting a HTTP 200. Although changing Redis
root-disable API is a much simpler way to resolve the problem, migrating
from HTTP 200 to HTTP 204 should be a better solution. Related tests and
documents are also updated accordingly.

APIImpact

Change-Id: If732a578009fd35436e810fb7ceceefd1ada3778
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
2018-03-02 20:57:23 +08:00
..
samples Return 204 instead of 200 for root-disable API 2018-03-02 20:57:23 +08:00
api-versions.inc [api-ref] Update style and instances api. 2018-01-25 22:55:13 +08:00
backups.inc [api-ref] Add sections for backups. 2018-02-27 19:28:38 +08:00
conf.py Merge "[api-ref] configure LogABug feature" 2016-11-15 23:57:02 +00:00
configurations.inc [api-ref] Update style and instances api. 2018-01-25 22:55:13 +08:00
database-instance-actions.inc [api-ref] Update style and instances api. 2018-01-25 22:55:13 +08:00
database-instance-logs.inc [api-ref] Add sections for instance logs. 2018-01-29 11:01:34 +08:00
database-instances.inc [api-ref]: update instance creating parameters. 2018-02-11 15:18:42 +08:00
databases.inc [api-ref] Update style and instances api. 2018-01-25 22:55:13 +08:00
datastores.inc [api-ref] Update style and instances api. 2018-01-25 22:55:13 +08:00
flavors.inc [api-ref] Update style and instances api. 2018-01-25 22:55:13 +08:00
index.rst [api-ref] Add sections for backups. 2018-02-27 19:28:38 +08:00
parameters.yaml [api-ref] Add sections for backups. 2018-02-27 19:28:38 +08:00
user-management.inc Return 204 instead of 200 for root-disable API 2018-03-02 20:57:23 +08:00