[katello-devel] API v2 - proposed changes in routes
Bryan Kearney
bkearney at redhat.com
Tue Mar 5 17:23:09 UTC 2013
On 03/05/2013 09:11 AM, Tomas Strachota wrote:
> On 03/05/2013 02:29 PM, Eric D Helms wrote:
>> On #2, if one of our core operating principles is that nearly everything
>> is scoped based on an organization, why would we want to abstract that
>> away and not make it explicit as part of resource look-up? Given that a
>> design goal of RESTful APIs is to be predictable, I would think the form
>> that includes organization at the trunk of the route is more predictable
>> and mimics how resources are structured.
>>
>
> The idea was not to get rid of the resource relations. The scope would
> still be there for collections. For example environments would look like:
>
> crate: POST /organization/ACME/
> list: GET /organization/ACME/environments/
> show: POST /environments/1/
> update: PUT /environments/1/
> destroy: DELETE /environments/1/
FWIW.. this is consistent with Candlepin. You get to a collection from
its parent, but the canonical location is at
/{OBJECT}/{ID}
-- bk
More information about the katello-devel
mailing list