Going through the API list

[Bryan Kearney]

I was going over the API list, and I had a couple of questoins:

  * POST /pools

Should we allow creating these directly?

  * GET /entitlements/consumer/{consumer_uuid}/product/{product_id} :

Is this still used?

  * POST /products/{product_uuid}/content/{content_id}

Should this be a put, or shouldd it be POST 
/products/{product_uuid}/contents

-- bk

[Justin Harris]

----- "Bryan Kearney" <bkearney(a)redhat.com&gt; wrote:

>  I was going over the API list, and I had a couple of questoins:
>  
>    * POST /pools
>  
>  Should we allow creating these directly? 
I guess the idea is that all pool creation comes from subscriptions?

>  
>    * GET /entitlements/consumer/{consumer_uuid}/product/{product_id} :
>  
>  Is this still used? 
Seems like the preferred way should be GET /products/{product_id}

>  
>    * POST /products/{product_uuid}/content/{content_id}
>  
>  Should this be a put, or shouldd it be POST 
>  /products/{product_uuid}/contents 
I think the restafarian way to go about this is have some entity that represents the
relationship
between a product and a content set, and post to that collection (so the ids would not be
in the URL).

I have no idea what this would be called.


>  
>  -- bk
>  
>  
>  _______________________________________________
>  candlepin mailing list
>  candlepin(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/candlepin

[Adrian Likins]

On 06/04/2010 09:28 AM, Justin Harris wrote:
>  ----- "Bryan Kearney"<bkearney(a)redhat.com>  wrote:
>     
> >    * POST /products/{product_uuid}/content/{content_id}
> >
> > Should this be a put, or shouldd it be POST
> > /products/{product_uuid}/contents
> >      
>  I think the restafarian way to go about this is have some entity that represents the
> relationship
>  between a product and a content set, and post to that collection (so the ids would not be
> in the URL).
>
>  I have no idea what this would be called.
>      
     That might come as part of the Content changes. There will be a 
PackageContent model, so
we can expose a resource for that, and POST to it.

Adrian

[Bryan Kearney]

On 06/04/2010 10:42 AM, Adrian Likins wrote:
>  On 06/04/2010 09:28 AM, Justin Harris wrote:
> > ----- "Bryan Kearney"<bkearney(a)redhat.com>   wrote:
> >
> >>     * POST /products/{product_uuid}/content/{content_id}
> >>
> >> Should this be a put, or shouldd it be POST
> >> /products/{product_uuid}/contents
> >>
> > I think the restafarian way to go about this is have some entity that represents the
> relationship
> > between a product and a content set, and post to that collection (so the ids would
> not be in the URL).
> >
> > I have no idea what this would be called.
> >
>        That might come as part of the Content changes. There will be a
>  PackageContent model, so
>  we can expose a resource for that, and POST to it.
>  
Are all of these used?

-- bk