Description of problem: We are using product Content Views to store RPM and Puppet modules together and freeze those per product release. The product Content Views are then bundled in Composite Content Views per hostgroup. The users shall only use the Composite Content Views. Please add an option to Hide Content Views from host/hostgroup assignment boxes. E.g. this can also be used to prepare a Content View without it being directly visible for all users. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
In addition we shouldn't publish a puppet environment for content views that have no puppet environments
Having this option to have a content view only for use by composite content views also can have a huge performance improvement. - publishing the repo for consumers is not require anymore - capsule synchronization is not required anymore for those content views
I am looking for feature where, if I have setup some filters in "roles", so when user is creating new hostgroup or modifying existing Host, he should only see contentviews with matching criteria in selection tab.
We have implemented a solution with using a separate Lifecycle environment for the compositecontentviews that shall be visible for the users. The library is then used for the building-block contentviews. The only downside is that we need to do 2 steps, a Publish and aPromote. To remvoe this inefficience there is a request to publuish directly to any lifeccle without the Library, see https://bugzilla.redhat.com/show_bug.cgi?id=1376474
Closing this RFE as original requester. The lifecycle environments fullfill this.