This part of Candlepin is coming from initially designing for hosted
products which are global in nature and that's likely why we added
this uniqueness constraint.
I don't see any real problem with removing it on the product name,
aside from the fact that an org could make two products with the same
name and in a lot of UI locations, would be unable to tell the
difference. (unless Katello enforces product name uniqueness per org,
which I guess it probably should)
A much larger possible solution is getting Candlepin's products
per-org, but this is likely a very big rats nest on our part, so we're
hoping this solution works, and Katello can do the needful in terms of
tracking orgs and their custom products.
I would file a bug and harass us/BK if it's an urgent change.
Cheers,
Devan
On Wed, Feb 8, 2012 at 11:47 AM, Tomas Strachota <tstrachota(a)redhat.com> wrote:
Hi all,
in Katello we currently can't create two custom products (each in different
Org) with the same name. There's uniqueness constraint on product names in
candlepin that doesn't allow it.
My question is:
Would it be possible to remove the constraint?
There are still unique product ids so from my point of view it seems safe to
remove the constraint from names. But my candlepin knowledge is not very
deep.
Are there any objections or better solutions you can see?
Prefixing the product name with org name wouldn't work here as the name is
displayed in subscription manager. Also sharing one candlepin product with
more katello products is no a good idea because they can have different
content.
Thanks for opinions and ideas
Tomas
_______________________________________________
katello-devel mailing list
katello-devel(a)redhat.com
https://www.redhat.com/mailman/listinfo/katello-devel