Allow overriding CSR attribute settings

[bwilcox]

Use Case

peadm is opinionated in the use of CSR attributes. Some customers have existing use for these attributes and the ability to override and add attributes would be beneficial.

Describe the Solution You Would Like

The ability to specify attributes and the values used for each host in a deployment.

Describe Alternatives You've Considered

Forking the project and changing the current hard-coded values for another set. But this creates something that requires on-going maintenance effort to keep current with changes.

[cyberious]

Would love to see this, it is keeping us for using in our existing environment, we use a bunch of the trusted facts including the challenge password for signing of Compile Masters

[cyberious]

For an example we lay this down in our cloud-init file.

  - path: /etc/puppetlabs/puppet/csr_attributes.yaml
    permissions: '0644'
    content: |
      ---
      csr_attributes:
        extension_requests:
          pp_application: "puppet/${role}"
          pp_environment: ${environment}
          pp_cluster: "${environment}_${cluster}"
          pp_zone: "${zone}"
          pp_cost_center: "${cost_center}"
          pp_role: "${pp_role}"
        custom_attributes:
          challengePassword: "${sslChallenge}"

[bwilcox]

#69

There's a working example. Might not be the best approach. I'm welcome to suggestions.

[reidmv]

Fixed in #76