Description of problem:
Currently there is no way to add multiple Puppet modules to a content view. Adding 5 modules takes quite a while. Creating a view with 20-30 modules (which might be common) probably takes an excruciatingly long time.
It would be great if we could figure out a way to implement some kind of mass-add modules.
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
We have also run into this issue. Here are two possible ways of addressing it, although I'm sure there are more:
1) Take advantage of puppet module metadata (in either Modulefile or metadata.json) to automatically detect missing dependencies in the content view and easily run through all of them to select which version you want. Keep doing this until all dependencies are resolved.
2) Let a user provide a Puppetfile with a listing of puppet modules that should be in the content view. This could either resolve dependencies (puppet-librarian style) or require all dependencies be included (r10k style). Either way, ti would make this a faster process.
Here's a post about using Librarian: https://bitbin.de/blog/2015/05/using-librarian-with-katello/
BZ1127382 breaks hammer puppet-module though, but even if it was working, it's absurd the hoops to jump through. I should be able to add a puppet module to a content view
Hit submit too early --
I should be able to add a puppet module to a content view based solely on version and name (in the CLI)
For the UI case though that Erik is asking about, not sure how to make that part easier, you always have to select a version (explicit or latest) for each module.
*** This bug has been marked as a duplicate of bug 1154400 ***