Manager certificate permissions if manage_certificates true

[ehelms]

Reviving an old PR with fresh updates. The idea behind this is at the users choice, the module can manage the certificates for the smart-proxy. When true, this will copy certificates provided into a known and controlled location, ensuring the right owner and group are set on them such that the smart-proxy can operate as intended. This is borrowed from, and can replace, puppet-certs implementation and help prevent an ordering problem with certificate generation and deployment. And this can provide a native way to indicate when a service restart is needed.

[ekohl]

We also have some code to manage Puppet certificates. I'm not entirely sure if this will conflict, but want you to be aware of it:

puppet-foreman_proxy/manifests/config.pp

Lines 114 to 135 in af23995

	unless $foreman_proxy::puppetca or $foreman_proxy::puppet {
	# The puppet-agent doesn't create a puppet user and group
	# but the foreman proxy still needs to be able to read the agent's private key
	if $foreman_proxy::manage_puppet_group and $foreman_proxy::ssl {
	if !defined(Group[$foreman_proxy::puppet_group]) {
	group { $foreman_proxy::puppet_group:
	ensure => 'present',
	before => User[$foreman_proxy::user],
	}
	}
	$ssl_dirs_and_files = [
	$foreman_proxy::ssldir,
	"${foreman_proxy::ssldir}/private_keys",
	$foreman_proxy::ssl_ca,
	$foreman_proxy::ssl_key,
	$foreman_proxy::ssl_cert,
	]
	file { $ssl_dirs_and_files:
	group => $foreman_proxy::puppet_group,
	}
	}
	}

[ehelms]

I'm stuck on why the tests are not seeing the resource present.

[alexjfisher]

I'm stuck on why the tests are not seeing the resource present.

Use #{etc_dir} in the expected file path (as conf_dir is /usr/local/etc/foreman-proxy on FreeBSD)?