Installer support for Foreman plugins
The installer should support installing plugins on top of Foreman, and provide classes which can install and configure plugins appropriately for most/all of those we provide packages for.
It should also support installing the optional Foreman components like foreman-compute, -libvirt, -vmware etc.
Refs #3308 - Auto-create mappings hash from detected plugin/compute classes
#3 Updated by Dominic Cleal about 7 years ago
Greg Sutcliffe wrote:
I assume all we really need here is an array of extra packages to install?
I think we should provide more than that, bearing in mind the kafo installer interface, i.e.
--foreman-libvirt=true is clearer than
For plugins, I don't think a package install is sufficient. I'd say an additional Puppet class that can be enabled is needed (especially if it can use kafo's module + parameter support), as we'll probably want to provide configuration as well as just a package. Consider column_view as an example, which has an associated config file. Even for plugins that don't have config yet, we can seamlessly add it later.
#7 Updated by Dominic Cleal almost 7 years ago
- Status changed from Assigned to New
- Assignee deleted (
Some support for plugins went into the foreman module, thanks to Ewoud: https://github.com/theforeman/puppet-foreman/pull/132
However we're missing support in foreman-installer itself (blocked on #3887), plus support for extra meta-packages.
#13 Updated by Ewoud Kohl van Wijngaarden almost 7 years ago
There's already foreman::plugin::puppetdb: https://github.com/theforeman/puppet-foreman/blob/master/manifests/plugin/puppetdb.pp
#16 Updated by Dominic Cleal almost 7 years ago
- Status changed from Assigned to Ready For Testing
- Assignee set to Greg Blomquist