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
Thepuppet.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, andpuppetserver ca
. Nearly all of the settings listed in the configuration reference can be set inpuppet.conf
. -
environment.conf: Per-environment settings
Environments are isolated groups of agent nodes. Any environment can contain anenvironment.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
Thefileserver.conf
file configures custom static mount points for Puppet’s file server. If custom mount points are present,file
resources can access them with theirsource
attributes. -
puppetdb.conf: PuppetDB server locations
Thepuppetdb.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
Theautosign.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 useautosign.conf
. -
csr_attributes.yaml: Certificate extensions
Thecsr_attributes.yaml
file defines custom data for new certificate signing requests (CSRs). -
custom_trusted_oid_mapping.yaml: Short names for cert extension OIDs
Thecustom_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
Thepuppet-device
subcommand retrieves catalogs from the primary Puppet server and applies them to remote devices. Devices to be managed by thepuppet-device
subcommand are configured indevice.conf
. -
routes.yaml: Advanced plugin routing
Theroutes.yaml
file overrides configuration settings involving indirector termini, and allows termini to be set in greater detail thanpuppet.conf
allows.