fixes #15063 - Set answers for foreman client certs

[ekohl]

theforeman/puppet-foreman@ec8c6c2 exposes the foreman client certificates through parameters. Since Katello wants to change these from puppet to custom handling, these must be set. puppet-certs currently attempts to do so through foreman-rake config. Since puppet-foreman has started to set these in settings.yaml, they can't be overridden anymore. By setting these in the answers file, we avoid that conflict.

Note I didn't test this yet, but I believe this will become a problem so I opened this to track it.

[theforeman-bot]

There were the following issues with the commit message:

• 1608c1e must be in the format fixes #redmine_number - brief description
• commit message for 1608c1e is not wrapped at 72nd column

If you don't have a ticket number, please create an issue in Redmine, selecting the appropriate project.

More guidelines are available in Coding Standards or on the Foreman wiki.

---

This message was auto-generated by Foreman's prprocessor

[stbenjam]

This replaces theforeman/puppet-certs#87, right?

[stbenjam]

Need to get this in ASAP, as it seems to have broken our nightly install:

 /Stage[main]/Certs::Foreman/Exec[foreman_certs_config]/returns: change from notrun to 0 failed: /usr/share/foreman/script/foreman-rake config --      -k ssl_ca_file -v '/etc/foreman/proxy_ca.pem'      -k ssl_certificate -v '/etc/foreman/client_cert.pem'      -k ssl_priv_key -v '/etc/foreman/client_key.pem' returned 1 instead of one of [0]

[stbenjam]

I think the paths should be:

  $foreman_client_cert    = '/etc/foreman/client_cert.pem'
  $foreman_client_key     = '/etc/foreman/client_key.pem'
  $foreman_ssl_ca_cert    = '/etc/foreman/proxy_ca.pem'

[stbenjam]

With these paths above, and removing the stanzas from puppet-certs (the ones theforeman/puppet-certs#87 tried to change) entirely, I get a clean install.

[stbenjam]

Closed in favor of #335