Actions
Bug #12496
closedAllow more control over the puppet server configuration through the installer
Description
I'm a current user of Foreman and am trying to migrate to Katello but am running into some restrictions when configuring the puppet master to match our current workflow.
For example:
- We use the future parser. Under the foreman installer there is an option to set this. Under the Katello installer I have worked around the lack of this option by setting
puppet::server_parser: future
in /var/lib/heira/common.yaml. - We also use a git branch to puppet environment workflow and I'm not ready to migrate to the Katello content view model. Again I was able to work around this by setting
puppet::server_git_repo: true
through hiera. - Finally, we also use exported resources through PuppetDB. I have not been able to work around this using hiera because /usr/share/katello-installer/modules/capsule/manifests/init.pp explicitly sets
puppet::server_storeconfigs_backend
to false.
What I would like to see:
- I'm okay with using hiera to set unsupported puppet server parameters, but it would be nice to support these through the katello installer so I can keep all of my configuration in a single location (answers.katello-installer.yaml).
- The capsule manifest should not explicitly set
puppet::server_storeconfigs_backend
or any other parameters for the puppet class that are not controllable in some way through the installer and that are not critical to the correct operation of the puppet master with Katello.
Environment:
CentOS Linux release 7.1.1503 (Core)
katello-installer: 2.3.1-6.el7
foreman: 1.9.3-1.el7
Thank you
Updated by Eric Helms over 8 years ago
- Translation missing: en.field_release set to 86
- Triaged changed from No to Yes
Updated by Eric Helms over 8 years ago
- Status changed from New to Resolved
The puppet-foreman_proxy module is now top level in the installer so any options that are exposed by it are now available.
Actions