Actions
Refactor #35985
closed
Move katello certificate integration into puppet-puppet
Difficulty:
Triaged:
Yes
Pull request:
https://github.com/theforeman/puppet-puppet/pull/862, https://github.com/theforeman/puppet-foreman_proxy_content/pull/440, https://github.com/theforeman/foreman-installer/pull/828, https://github.com/theforeman/foreman-documentation/pull/1947, https://github.com/theforeman/forklift/pull/1649, https://github.com/theforeman/foreman-documentation/pull/2108
Description
Today we have --puppet-foreman-proxy-content-puppet true, and then the user needs to supply certificate paths to our theforeman/puppet module. Instead we should move this integration into our theforeman/puppet module.
I'm proposing a boolean parameter which can be set via Hiera. Then in our installer's Hiera configuration we can set this for the appropriate scenarios.
Updated by
Added by Ewoud Kohl van Wijngaarden over 2 years ago
Added by Ewoud Kohl van Wijngaarden about 2 years ago
Refs #35985 - Rely on theforeman/puppet to do integration
The integration is moved into theforeman/puppet so this is no longer
needed.
Added by Ewoud Kohl van Wijngaarden about 2 years ago
Fixes #35985 - Use Katello integration in theforeman/puppet
Actions
Refs #35985 - Implement optional Katello integration
Katello uses a different certificate structure. This moves over the
integration bits from puppet-foreman_proxy_content to this module. It
also means fewer variables need to be set in the installer itself.