Puppet's configuration files

Puppet settings can be configured in the main config file, called puppet.conf. There are several additional configuration files, for new settings and ones that need to be in separate files with complex data structures.

  • puppet.conf: The main config file

    The puppet.conf file is Puppet’s main config file. It configures all of the Puppet commands and services, including Puppet agent, the primary Puppet server, Puppet apply, and puppetserver ca. Nearly all of the settings listed in the configuration reference can be set in puppet.conf.

  • environment.conf: Per-environment settings

    Environments are isolated groups of agent nodes. Any environment can contain an environment.conf file. This file can override several settings whenever the primary server is serving nodes assigned to that environment.

  • fileserver.conf: Custom fileserver mount points

    The fileserver.conf file configures custom static mount points for Puppet’s file server. If custom mount points are present, file resources can access them with their source attributes.

  • puppetdb.conf: PuppetDB server locations

    The puppetdb.conf file configures how Puppet connects to one or more servers. It is only used if you are using PuppetDB and have connected your primary server to it.

  • autosign.conf: Basic certificate autosigning

    The autosign.conf file can allow certain certificate requests to be automatically signed. It is only valid on the CA primary Puppet server; a primary server not serving as a CA does not use autosign.conf.

  • csr_attributes.yaml: Certificate extensions

    The csr_attributes.yaml file defines custom data for new certificate signing requests (CSRs).

  • custom_trusted_oid_mapping.yaml: Short names for cert extension OIDs

    The custom_trusted_oid_mapping.yaml file lets you set your own short names for certificate extension object identifiers (OIDs), which can make the $trusted variable more useful.

  • device.conf: Network hardware access

    The puppet-device subcommand retrieves catalogs from the primary Puppet server and applies them to remote devices. Devices to be managed by the puppet-device subcommand are configured in device.conf.

  • routes.yaml: Advanced plugin routing

    The routes.yaml file overrides configuration settings involving indirector termini, and allows termini to be set in greater detail than puppet.conf allows.