To PUT or to POST
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Unassigned |
Bug Description
Question to the list that has some merit...
Jason
-----Original Message-----
From: <email address hidden>
[mailto:<email address hidden>] On
Behalf Of Mellquist, Peter
Sent: Wednesday, July 20, 2011 5:46 PM
To: <email address hidden>
Subject: [Openstack] [Keystone] usage of PUT and POST in APIs
Looking through the latest Keystone code and developer guide I have noticed
some differences in the usage of PUT and POST CRUD operations.
Resource Creation admin.py Developer Guide Says
.......
Tenant PUT or POST PUT in table 5.2.4 OR POST in
section 5.4.1 ?
Tenant Group PUT or POST NA
Users PUT or POST PUT in table 5.2.2
Global Group PUT or POST NA
Role Ref POST POST in table 5.2.6 and section
5.6.4
Endpoints POST POST in table 5.2.5 and section
5.5.4
Questions:
Is there any reason why Tenants and Users allow PUT and POST for creation
while Roles and Endpoints only allow POST?
Would it be possible to go only with POSTs in the above areas?
The developer guide does not match the current code in the above areas,
these may just be typos at this stage but it would be good to clarify what
the real APIs should be.
Peter.
Looks like we got to stick to POSTs as a part of effort to standardize operations across openstack.