Content generator metadata change proposal
by Tomas Kopecek
Hello,
we've a proposal to limit metadata to only one content generator. Currently
there is a theoretical option to import outputs of more CGs in one big
import. Question is if anybody ever used this option. Otherwise it looks
better to limit it just to one CG per import. Having more of these is
causing some additional complexity in code and even in policies which
should handle volumes, etc. It is more discussed in
https://pagure.io/koji/issue/2511
So,
1) is someone using multiple CG ids in one import?
2) are there any reasons to have this option even in future?
--
Tomas Kopecek <tkopecek(a)redhat.com>
RHEL Build Development, RedHat
2 years, 6 months
