trove/return-http-204-for-disable-root-api-a818fc41fd6e75eb.yaml at 4860f523d45df502e2d1005df3db4121c7795fe0 - trove - OpenDev: Free Software Needs Free Tools

openstack/trove

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

6 lines

168 B

YAML

Raw Blame History

 ---
 fixes:
   - |
     Peviously root disable API returns a HTTP 200 response without any content,
     a HTTP 204 reponse which is more appropriate will be returned now.