Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6247

Allow for certname_fact setting to be used to override default fqdn

    Details

    • Type: Improvement
    • Status: Accepted
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Currently there is no way to customize how a node determines what certificate name it should use:
      the certname value in the puppet.conf
      or failing that, using the fqdn returned by facter.

      We should allow for a certname_fact setting to allow this value to be overridden, allowing for a generic puppet.conf file to be reused across images / templates.

      For example, in AWS this would allow for a puppet.conf that contains a certname_fact = ec2_metadata.instance-id, bypassing any need to execute a puppet config set command at instance boot.

      This, combined with PUP-6239 would enable for the reuse of a standard puppet.conf file for agents across an environment that is dynamically scaling and not conforming to standard hostname based classification (aka cloud environments).

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              cbarker Chris Barker
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Zendesk Support