allow for setting `certname` parameter in `[master]` config about puppet-puppet HOT 4 CLOSED

as an alternative, setting dns_alt_names through this module would do the trick, I believe.

from puppet-puppet.

You are right indeed.
You can both have two different certnames and use dns_alt_names or keep the same certname for the two puppetmasters. Note anyway that with the template => parameter you can override the default configuration file (either for client or master) with a custom one, where you can provide any configuration you need.
If you find a sane way to manage this case with other parameters, feel free to submit a pull request, it's always appreciated.

from puppet-puppet.

You can both have two different certnames and use dns_alt_names or keep
the same certname for the two puppetmasters. Note anyway that with the
template => parameter you can override the default configuration file
(either for client or master) with a custom one, where you can provide
any configuration you need.
If you find a sane way to manage this case with other parameters, feel
free to submit a pull request, it's always appreciated.

Would it hurt if I just add a dns_alt_names parameter to the puppet
class and adapt the server template accordingly? The parameter would
then have no effect at all when set on a client. Or should I check if
the new parameter is set for a client and then raise an error (is that
possible? how?)?

from puppet-puppet.

It's ok to add the dns_alt_names parameter and then use it in the template if defined.
Follow the logic used for other parameters.
(Sadly the module is poorly documented, and most of the available options are not explained)

from puppet-puppet.