[katello-devel] DESIGN: As a Katello user, I would like Candlepin to be in charge of the subscription portion of the activation key logic

[Bryan Kearney]

On 02/27/2013 11:02 AM, Dmitri Dolguikh wrote:
> Functionality already exists on the Candlepin side. See docs for
> assocation [1] and de-association [2] of activation keys with/from a
> pool. Katello API exposes assocation/de-association operations through
> POST api/activation_keys/:id/pools and DELETE
> api/activation_keys/:id/pools/:pool_id respectively. Internally this is
> implemented as a many-to-many relationship between pools and activation
> keys.
>
> Required changes:
>   - Drop "key_pools" join table and corresponding activation keys-pools
> association; replace with calls described at [1] and [2].
>   - (potentially?) Add elastic search index for activation key/pool
> association, based on pool id.
>
> Thoughts/opinions?
> -d
>
>
> [1].
> http://www.candlepinproject.org/apidoc/post/activation_keys/activation_key_id/pools/pool_id/
>
> [2]. De-association of an activation key from a pool:
> http://www.candlepinproject.org/apidoc/delete/activation_keys/activation_key_id/pools/pool_id/


I would add to this that during registratoin the keys need to make their 
way to Candlepin. Assuming you have that I think you are good.
-- bk