refreshing entitlements/pools by product

[James Bowes]

I was looking at PUT /entitlements/product/{product_id} today. That will
regenerate the certificates for all entitlements that grant product_id.

This call isn't sufficient though. since it doesn't refresh the pool
data, candlepin might miss out on attributes changes. IMO it makes more
sense to have a call that does a refresh_pools based on product id,
rather than based on owner id. But, since we have no stored old product
data, we'd have to then go ahead and regenerate all entitlements in the
affected pools.

Does it make sense to have this call be under /entitlements, or should
it be under /products? maybe something like PUT
/products/{product_id}/subscriptions ?

-James

[Bryan Kearney]

On 06/19/2012 01:58 PM, James Bowes wrote:
> I was looking at PUT /entitlements/product/{product_id} today. That will
> regenerate the certificates for all entitlements that grant product_id.
>
> This call isn't sufficient though. since it doesn't refresh the pool
> data, candlepin might miss out on attributes changes. IMO it makes more
> sense to have a call that does a refresh_pools based on product id,
> rather than based on owner id. But, since we have no stored old product
> data, we'd have to then go ahead and regenerate all entitlements in the
> affected pools.
>
> Does it make sense to have this call be under /entitlements, or should
> it be under /products? maybe something like PUT
> /products/{product_id}/subscriptions ?

can it be

PUT /entitlements/product/{product_id}?regenCerts=True

?

[Devan Goodwin]

On 06/19/2012 02:58 PM, James Bowes wrote:
> I was looking at PUT /entitlements/product/{product_id} today. That will
> regenerate the certificates for all entitlements that grant product_id.
>
> This call isn't sufficient though. since it doesn't refresh the pool
> data, candlepin might miss out on attributes changes. IMO it makes more
> sense to have a call that does a refresh_pools based on product id,
> rather than based on owner id. But, since we have no stored old product
> data, we'd have to then go ahead and regenerate all entitlements in the
> affected pools.
>
> Does it make sense to have this call be under /entitlements, or should
> it be under /products? maybe something like PUT
> /products/{product_id}/subscriptions ?

^^ Seems reasonable to me as you're acting on products.