Puppet has about 200 settings, all of which are listed in the configuration reference. Most of the time, you interact with only a couple dozen of them. This page lists the most important ones, assuming that you're okay with default values for things like the port Puppet uses for network traffic. See the configuration reference for more details on each.
There are a lot of settings that are rarely useful but still make sense, but there are also at least a hundred that are not configurable at all. This is a Puppet design choice. Because of the way Puppet code is arranged, the settings system is the easiest way to publish global constants that are dynamically initialized on startup. This means a lot of things have been introduced to Puppet as configurable settings regardless of whether they needed to be configurable.
For a full list of Puppet settings, see the configuration reference.
Settings for agents (all nodes)
The following settings for agents are listed approximately
in order of importance. Most of these can go in either
[agent] sections, or be specified on the
server— The primary server to request configurations from. Defaults to
puppet. Change it if that’s not your server’s name.
report_server— If you’re using multiple Puppet primary servers, you’ll need to centralize the CA. One of the ways to do this is by configuring
ca_serveron all agents. See Scaling Puppet Server with compile servers for more details. The
report_serversetting works the same way, although whether you need to use it depends on how you’re processing reports.
certname— The node’s certificate name, and the unique identifier it uses when requesting catalogs. Defaults to the fully qualified domain name.
For best compatibility, limit the value of
certnameto only use lowercase letters, numbers, periods, underscores, and dashes. That is, it matches
The special value
cais reserved, and can’t be used as the certname for a normal node.
environment— The environment to request when contacting the primary server. It’s only a request, though; the primary server’s ENC can override this if it chooses. Defaults to
sourceaddress— The address on a multihomed host to use for the agent’s communication with the primary server.
node_name_valuesetting), we don’t generally recommend it. It allows you to re-use one node certificate for many nodes, but it reduces security, makes it harder to reliably identify nodes, and can interfere with other features. Setting a non-certname node name is not officially supported in Puppet Enterprise.
These settings affect the way Puppet applies catalogs:
noop— If enabled, the agent won’t make any changes to the node. Instead, it looks for changes that would be made if the catalog were applied, and report to the primary server about what it would have done. This can be overridden per-resource with the
priority— Allows you to make the agent share CPU resources so that other applications have access to processing power while agent is applying a catalog.
report— Indicates whether to send reports. Defaults to true.
tags— Lets you limit the Puppet run to include only those resources with certain tags.
show_diff— Tools for debugging or learning more about an agent run. Useful when combined with the
usecacheonfailure— Indicates whether to fall back to the last known good catalog if the primary server fails to return a good catalog. The default behavior is usually what you want, but you might have a reason to disable it.
ignoreschedules— If you use schedules, this can be useful when doing an initial Puppet run to set up new nodes.
postrun_command— Commands to run on either side of a Puppet run.
ignore_plugin_errors— If set to false, the agent aborts the run if
pluginsyncfails. Defaults to true.
These settings affect the way Puppet agent acts when running as a long-lived service:
runinterval— How often to do a Puppet run, when running as a service.
waitforcert— Whether to keep trying if the agent can’t initially get a certificate. The default behavior is good, but you might have a reason to disable it.
Useful when running agent from cron
splaylimit— Together, these allow you to spread out agent runs. When running the agent as a daemon, the services usually have been started far enough out of sync to make this a non-issue, but it’s useful with cron agents. For example, if your agent cron job happens on the hour, you could set
splay = trueand
splaylimit = 60mto keep the primary server from getting briefly overworked and then left idle for the next 50 minutes.
daemonize— Whether to daemonize. Set this to false when running the agent from cron.
onetime— Whether to exit after finishing the current Puppet run. Set this to true when running the agent from cron.
For more information on these settings, see the configuration reference.
Settings for primary servers
Many of these settings are also important for standalone
Puppet apply nodes, because they act as their own primary server.
These settings go in the
[server] section, unless you’re using Puppet
apply in production, in which case put them in the
[main] section instead.
dns_alt_names— A list of hostnames the server is allowed to use when acting as a primary server. The hostname your agents use in their
serversetting must be included in either this setting or the primary server’s
certnamesetting. Note that this setting is only used when initially generating the primary server’s certificate — if you need to change the DNS names, you must:
Turn off the Puppet Server service (or your Rack server).
sudo puppetserver ca clean <SERVER'S CERTNAME>
sudo puppetserver ca generate <SERVER'S CERTNAME> --dns-alt-names <ALT NAME 1>,<ALT NAME 2>,...
Re-start the Puppet Server service.
environment_timeout— For better performance, you can set this to
unlimitedand make refreshing the primary server a part of your standard code deployment process.
environmentpath— Controls where Puppet finds directory environments. For more information on environments, see Creating environments.
basemodulepath— A list of directories containing Puppet modules that can be used in all environments. See modulepath for details.
reports— Which report handlers to use. For a list of available report handlers, see the report reference. You can also write your own report handlers. Note that the report handlers might require settings of their own.
digest_algorithm— To accept requests from older agents when using a remote filebucket, Puppet Server needs to specify
Puppet Server related settings
Puppet Server has its own configuration files;
consequently, there are several settings in
puppet.conf that Puppet Server ignores.
These features configure add-ons and optional features:
external_nodes— The ENC settings. If you’re using an ENC, set these to
execand the path to your ENC script, respectively.
storeconfigs_backend— Used for setting up PuppetDB. See the PuppetDB docs for details.
catalog_terminus— This can enable the optional static compiler. If you have lots of
fileresources in your manifests, the static compiler lets you sacrifice some extra CPU work on your primary server to gain faster configuration and reduced HTTPS traffic on your agents. See the indirection reference for details.
ca_ttl— How long newly signed certificates are valid. Deprecated.
autosign— Whether and how to autosign certificates. See Autosigning for detailed information.
For more information on these settings, see the configuration reference.