provide a mechanism to populate the dns_alt_names key in puppet.conf for the master.

[wolfspyre]

we likely want to provide the user the ability to populate dns_alt_names on their master.

[rendhalver]

This is definitely something that won't have much effect on a running system with a pre existing cert.
The dns_alt_names setting needs to be set before a cert is generated so should be part of system provisioning.

[divansantana]

@rendhalver So, initially I didn't quite understand your above comment when I read this issue and I noticed it as open and thought I'd try address it.

Anyway, now I understand what you were saying.

However, I'd still like to get this patch merged if you're OK with it. I've tested it properly and it works nicely.

It can and is useful to have it in, because (a) one can you this/your module to bootstrap/provision the initial Puppet CA. I've done that in our environment. So the first puppet CA starts up correctly using the module. (b) it's also nice to have this configured on the puppet CA after it's up and running from a consistency/clarity point of view, even though it has no impact once it's up and running. It does at least show to others how the CA was generated/initially configured.

PS. My previous PR had issues, this one should be fine.