Bug #6178
closed
The installer should use puppetlabs modules where possible
Description
Right now, a few of the modules the foreman-installer uses are theforeman specific. This creates problems when you want to use theforeman/foreman module in a larger puppet repository, and not install theforeman through foreman-installer. If the modules were using the standard puppetlabs modules as much as possible that would be really much more usable. foreman-installer is great for a simple test install, but in production environments I would imagine anyone would want to configure foreman as part of a much larger repository.
Updated by Dominic Cleal almost 10 years ago
Specifically which ones are you thinking of?
Updated by Walter Heck almost 10 years ago
Specifically puppetlabs/puppet is the toughest, as you can't have puppetlabs/puppet and theforeman/puppet in a single repo, and they don't share the same classes or anything. puppetlabs/puppet doesn't currently have ENC functionality, but that shouldn't be hard to put in a pull request.
Less important is theforeman/concat_native vs puppetlabs/concat.
Updated by Daniel Lobato Garcia almost 9 years ago
The concat vs concat_native issue is now fixed. https://github.com/theforeman/puppet-concat_native/commit/f7999137d9e17a27f4efdce23ce1f841cdabbd5d
Updated by Anonymous almost 7 years ago
- Status changed from New to Resolved
I think all that's possible for now has been done.
Updated by Ewoud Kohl van Wijngaarden almost 7 years ago
I'd like to merge theforeman-dhcp into voxpupuli-dhcp (formerly puppetlabs-dhcp) but we still need to merge quite a bit into their module that I think currently our module is of a higher quality. That means I agree that for now this can be closed.