Project

General

Profile

Actions
Copy link

Refactor #35985

closed

Move katello certificate integration into puppet-puppet

Added by Ewoud Kohl van Wijngaarden over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ewoud Kohl van Wijngaarden
Category:
-
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
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
Fixed in Releases:
Foreman - 3.6.0
Found in Releases:
Red Hat JIRA:

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.

Related issues 2 (0 open — 2 closed)

Related to Installer - Feature #33337: For Katello scenario, do not deploy Puppet by defaultClosedEric HelmsActions
Related to Foreman Maintain - Bug #36230: `foreman-maintain plugin purge-puppet` is using `foreman-proxy-content-puppet` which is no longer availableClosedEric HelmsActions
Actions
Copy link

Also available in: Atom PDF