puppet 5.0.0 → 5.0.1

data/man/man5/puppet.conf.5

@@ -1,8 +1,8 @@
 .\" generated with Ronn/v0.7.3
-.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPETCONF" "5" "May 2015" "Puppet Labs, LLC" "Puppet manual"
-\fBThis page is autogenerated; any changes will get overwritten\fR \fI(last generated on 2015\-05\-18 10:15:47 \-0700)\fR
+.TH "PUPPETCONF" "5" "June 2017" "Puppet Labs, LLC" "Puppet manual"
+\fBThis page is autogenerated; any changes will get overwritten\fR \fI(last generated on 2017\-06\-29 14:42:23 \-0700)\fR
 .
 .SH "Configuration Settings"
 .
@@ -30,7 +30,7 @@ The Puppet executables will ignore any setting that isn\'t relevant to their fun
 .IP "" 0
 .
 .P
-See the configuration guide \fIhttps://docs\.puppetlabs\.com/guides/configuring\.html\fR for more details\.
+See the configuration guide \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/config_about_settings\.html\fR for more details\.
 .
 .SS "agent_catalog_run_lockfile"
 A lock file to indicate that a puppet agent catalog run is currently in progress\. The file contains the pid of the process that holds the lock on the catalog run\.
@@ -56,21 +56,19 @@ Whether to allow a new certificate request to overwrite an existing certificate\
 .
 .IP "" 0
 .
-.IP "\(bu" 4
-\fIDefault\fR: false
+.SS "always_retry_plugins"
+Affects how we cache attempts to load Puppet resource types and features\. If true, then calls to \fBPuppet\.type\.<type>?\fR \fBPuppet\.feature\.<feature>?\fR will always attempt to load the type or feature (which can be an expensive operation) unless it has already been loaded successfully\. This makes it possible for a single agent run to, e\.g\., install a package that provides the underlying capabilities for a type or feature, and then later load that type or feature during the same run (even if the type or feature had been tested earlier and had not been available)\.
 .
-.IP "" 0
-.
-.SS "archive_file_server"
-During an inspect run, the file bucket server to archive files to if archive_files is set\.
+.P
+If this setting is set to false, then types and features will only be checked once, and if they are not available, the negative result is cached and returned for all subsequent attempts to load the type or feature\. This behavior is almost always appropriate for the server, and can result in a significant performance improvement for types and features that are checked frequently\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: $server
+\fIDefault\fR: true
 .
 .IP "" 0
 .
-.SS "archive_files"
-During an inspect run, whether to archive files whose contents are audited to a file bucket\.
+.SS "app_management"
+This setting has no effect and will be removed in a future Puppet version\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: false
@@ -101,7 +99,7 @@ If a custom policy executable is configured, the CA puppet master will run it ev
 If a certificate request is not autosigned, it will persist for review\. An admin user can use the \fBpuppet cert sign\fR command to manually sign it, or can delete the request\.
 .
 .P
-For info on autosign configuration files, see the guide to Puppet\'s config files \fIhttps://docs\.puppetlabs\.com/guides/configuring\.html\fR\.
+For info on autosign configuration files, see the guide to Puppet\'s config files \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/config_about_settings\.html\fR\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: $confdir/autosign\.conf
@@ -112,7 +110,7 @@ For info on autosign configuration files, see the guide to Puppet\'s config file
 The search path for \fBglobal\fR modules\. Should be specified as a list of directories separated by the system path separator character\. (The POSIX path separator is \':\', and the Windows path separator is \';\'\.)
 .
 .P
-These are the modules that will be used by \fIall\fR environments\. Note that the \fBmodules\fR directory of the active environment will have priority over any global directories\. For more info, see https://docs\.puppetlabs\.com/puppet/latest/reference/environments\.html
+These are the modules that will be used by \fIall\fR environments\. Note that the \fBmodules\fR directory of the active environment will have priority over any global directories\. For more info, see \fIhttps://docs\.puppet\.com/puppet/latest/reference/environments\.html\fR
 .
 .IP "\(bu" 4
 \fIDefault\fR: $codedir/modules:/opt/puppetlabs/puppet/modules
@@ -287,7 +285,7 @@ This is the name used when managing a node\'s permissions in auth\.conf \fIhttps
 A node\'s certname is available in Puppet manifests as \fB$trusted[\'certname\']\fR\. (See Facts and Built\-In Variables \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/lang_facts_and_builtin_vars\.html\fR for more details\.)
 .
 .IP "\(bu" 4
-For best compatibility, you should limit the value of \fBcertname\fR to only use letters, numbers, periods, underscores, and dashes\. (That is, it should match \fB/A[a\-z0\-9\._\-]+Z/\fR\.)
+For best compatibility, you should limit the value of \fBcertname\fR to only use lowercase letters, numbers, periods, underscores, and dashes\. (That is, it should match \fB/A[a\-z0\-9\._\-]+Z/\fR\.)
 .
 .IP "\(bu" 4
 The special value \fBca\fR is reserved, and can\'t be used as the certname for a normal node\.
@@ -340,9 +338,10 @@ Code to parse directly\. This is essentially only used by \fBpuppet\fR, and shou
 .SS "codedir"
 The main Puppet code directory\. The default for this setting is calculated based on the user\. If the process is running as root or the user that Puppet is supposed to run as, it defaults to a system directory, but if it\'s running as any other user, it defaults to being in the user\'s home directory\.
 .
-.TP
-\fIDefault\fR:
-
+.IP "\(bu" 4
+\fIDefault\fR: Unix/Linux: /etc/puppetlabs/code \-\- Windows: C:\eProgramData\ePuppetLabs\ecode \-\- Non\-root user: ~/\.puppetlabs/etc/code
+.
+.IP "" 0
 .
 .SS "color"
 Whether to use colors when logging to the console\. Valid values are \fBansi\fR (equivalent to \fBtrue\fR), \fBhtml\fR, and \fBfalse\fR, which produces no color\. Defaults to false on Windows, as its console does not support ansi colors\.
@@ -356,7 +355,7 @@ Whether to use colors when logging to the console\. Valid values are \fBansi\fR
 The main Puppet configuration directory\. The default for this setting is calculated based on the user\. If the process is running as root or the user that Puppet is supposed to run as, it defaults to a system directory, but if it\'s running as any other user, it defaults to being in the user\'s home directory\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: /etc/puppetlabs/puppet
+\fIDefault\fR: Unix/Linux: /etc/puppetlabs/puppet \-\- Windows: C:\eProgramData\ePuppetLabs\epuppet\eetc \-\- Non\-root user: ~/\.puppetlabs/etc/puppet
 .
 .IP "" 0
 .
@@ -380,7 +379,7 @@ The name of the puppet config file\.
 How to determine the configuration version\. By default, it will be the time that the configuration is parsed, but you can provide a shell script to override how the version is determined\. The output of this script will be added to every log message in the reports, allowing you to correlate changes on your hosts to the source version on the server\.
 .
 .P
-Setting a global value for config_version in puppet\.conf is not allowed (but it can be overridden from the commandline)\. Please set a per\-environment value in environment\.conf instead\. For more info, see https://docs\.puppetlabs\.com/puppet/latest/reference/environments\.html
+Setting a global value for config_version in puppet\.conf is not allowed (but it can be overridden from the commandline)\. Please set a per\-environment value in environment\.conf instead\. For more info, see \fIhttps://docs\.puppet\.com/puppet/latest/reference/environments\.html\fR
 .
 .SS "configprint"
 Print the value of a specific configuration setting\. If the name of a setting is provided for this, then the value is printed and puppet exits\. Comma\-separate multiple values\. For a list of all values, specify \'all\'\.
@@ -427,7 +426,7 @@ Whether to send the process into the background\. This defaults to true on POSIX
 .IP "" 0
 .
 .SS "data_binding_terminus"
-Where to retrive information about data\.
+This setting has been deprecated\. Use of any value other than \'hiera\' should instead be configured in a version 5 hiera\.yaml\. Until this setting is removed, it controls which data binding terminus to use for global automatic data binding (across all environments)\. By default this value is \'hiera\'\. A value of \'none\' turns off the global binding\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: hiera
@@ -528,24 +527,50 @@ Valid values for this setting are:
 \fBdeprecations\fR \-\-\- disables deprecation warnings\.
 .
 .IP "\(bu" 4
+\fBundefined_variables\fR \-\-\- disables warnings about non existing variables\.
+.
+.IP "\(bu" 4
+\fBundefined_resources\fR \-\-\- disables warnings about non existing resources\.
+.
+.IP "\(bu" 4
 \fIDefault\fR: []
 .
 .IP "" 0
 .
 .SS "dns_alt_names"
-The comma\-separated list of alternative DNS names to use for the local host\.
+A comma\-separated list of alternate DNS names for Puppet Server\. These are extra hostnames (in addition to its \fBcertname\fR) that the server is allowed to use when serving agents\. Puppet checks this setting when automatically requesting a certificate for Puppet agent or Puppet Server, and when manually generating a certificate with \fBpuppet cert generate\fR\.
 .
 .P
-When the node generates a CSR for itself, these are added to the request as the desired \fBsubjectAltName\fR in the certificate: additional DNS labels that the certificate is also valid answering as\.
+In order to handle agent requests at a given hostname (like "puppet\.example\.com"), Puppet Server needs a certificate that proves it\'s allowed to use that name; if a server shows a certificate that doesn\'t include its hostname, Puppet agents will refuse to trust it\. If you use a single hostname for Puppet traffic but load\-balance it to multiple Puppet Servers, each of those servers needs to include the official hostname in its list of extra names\.
 .
 .P
-This is generally required if you use a non\-hostname \fBcertname\fR, or if you want to use \fBpuppet kick\fR or \fBpuppet resource \-H\fR and the primary certname does not match the DNS name you use to communicate with the host\.
+\fBNote:\fR The list of alternate names is locked in when the server\'s certificate is signed\. If you need to change the list later, you can\'t just change this setting; you also need to:
 .
-.P
-This is unnecessary for agents, unless you intend to use them as a server for \fBpuppet kick\fR or remote \fBpuppet resource\fR management\.
+.IP "\(bu" 4
+On the server: Stop Puppet Server\.
+.
+.IP "\(bu" 4
+On the CA server: Revoke and clean the server\'s old certificate\. (\fBpuppet cert clean <NAME>\fR)
+.
+.IP "\(bu" 4
+On the server: Delete the old certificate (and any old certificate signing requests) from the ssldir \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/dirs_ssldir\.html\fR\.
+.
+.IP "\(bu" 4
+On the server: Run \fBpuppet agent \-t \-\-ca_server <CA HOSTNAME>\fR to request a new certificate
+.
+.IP "\(bu" 4
+On the CA server: Sign the certificate request, explicitly allowing alternate names (\fBpuppet cert sign \-\-allow\-dns\-alt\-names <NAME>\fR)\.
+.
+.IP "\(bu" 4
+On the server: Run \fBpuppet agent \-t \-\-ca_server <CA HOSTNAME>\fR to retrieve the cert\.
+.
+.IP "\(bu" 4
+On the server: Start Puppet Server again\.
+.
+.IP "" 0
 .
 .P
-It is rarely necessary for servers; it is usually helpful only if you need to have a pool of multiple load balanced masters, or for the same master to respond on two physically separate networks under different names\.
+To see all the alternate names your servers are using, log into your CA server and run \fBpuppet cert list \-a\fR, then check the output for \fB(alt names: \.\.\.)\fR\. Most agent nodes should NOT have alternate names; the only certs that should have them are Puppet Server nodes that you want other agents to trust\.
 .
 .SS "document_all"
 Whether to document all resources when using \fBpuppet doc\fR to generate manifest documentation\.
@@ -564,12 +589,11 @@ The environment Puppet is running in\. For clients (e\.g\., \fBpuppet agent\fR)
 .IP "" 0
 .
 .SS "environment_data_provider"
-The name of a registered environment data provider\. The two built in and registered providers are \'none\' (no environment specific data), and \'function\' (environment specific data obtained by calling the function \'environment::data()\')\. Other environment data providers may be registered in modules on the module path\. For such custom data providers see the respective module documentation\.
+The name of a registered environment data provider used when obtaining environment specific data\. The three built in and registered providers are \'none\' (no data), \'function\' (data obtained by calling the function \'environment::data()\') and \'hiera\' (data obtained using a data provider configured using a hiera\.yaml file in root of the environment)\. Other environment data providers may be registered in modules on the module path\. For such custom data providers see the respective module documentation\. This setting is deprecated\.
 .
-.IP "\(bu" 4
-\fIDefault\fR: none
-.
-.IP "" 0
+.TP
+\fIDefault\fR:
+
 .
 .SS "environment_timeout"
 How long the Puppet master should cache data it loads from an environment\. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y)\. A value of \fB0\fR will disable caching\. This setting can also be set to \fBunlimited\fR, which will cache environments until the master is restarted or told to refresh the cache\.
@@ -600,7 +624,7 @@ We don\'t recommend using any value other than \fB0\fR or \fBunlimited\fR, since
 A search path for directory environments, as a list of directories separated by the system path separator character\. (The POSIX path separator is \':\', and the Windows path separator is \';\'\.)
 .
 .P
-This setting must have a value set to enable \fBdirectory environments\.\fR The recommended value is \fB$codedir/environments\fR\. For more details, see https://docs\.puppetlabs\.com/puppet/latest/reference/environments\.html
+This setting must have a value set to enable \fBdirectory environments\.\fR The recommended value is \fB$codedir/environments\fR\. For more details, see \fIhttps://docs\.puppet\.com/puppet/latest/reference/environments\.html\fR
 .
 .IP "\(bu" 4
 \fIDefault\fR: $codedir/environments
@@ -616,10 +640,41 @@ Whether each resource should log when it is being evaluated\. This allows you to
 .IP "" 0
 .
 .SS "external_nodes"
-An external command that can produce node information\. The command\'s output must be a YAML dump of a hash, and that hash must have a \fBclasses\fR key and/or a \fBparameters\fR key, where \fBclasses\fR is an array or hash and \fBparameters\fR is a hash\. For unknown nodes, the command should exit with a non\-zero exit code\.
+The external node classifier (ENC) script to use for node data\. Puppet combines this data with the main manifest to produce node catalogs\.
+.
+.P
+To enable this setting, set the \fBnode_terminus\fR setting to \fBexec\fR\.
+.
+.P
+This setting\'s value must be the path to an executable command that can produce node information\. The command must:
+.
+.IP "\(bu" 4
+Take the name of a node as a command\-line argument\.
+.
+.IP "\(bu" 4
+.
+.IP "\(bu" 4
+\fBclasses\fR \-\-\- A list of classes, as an array or hash\.
+.
+.IP "\(bu" 4
+\fBenvironment\fR \-\-\- A string\.
+.
+.IP "\(bu" 4
+\fBparameters\fR \-\-\- A list of top\-scope variables to set, as a hash\.
+.
+.IP "" 0
+
+.
+.IP "\(bu" 4
+For unknown nodes, exit with a non\-zero exit code\.
+.
+.IP "" 0
+.
+.P
+Generally, an ENC script makes requests to an external data source\.
 .
 .P
-This command makes it straightforward to store your node mapping information in other data sources like databases\.
+For more info, see the ENC documentation \fIhttps://docs\.puppet\.com/puppet/latest/nodes_external\.html\fR\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: none
@@ -726,7 +781,7 @@ The group puppet master should run as\.
 The hiera configuration file\. Puppet only reads this file on startup, so you must restart the puppet master every time you edit it\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: $codedir/hiera\.yaml
+\fIDefault\fR: $confdir/hiera\.yaml\. However, if a file exists at $codedir/hiera\.yaml, Puppet uses that instead\.
 .
 .IP "" 0
 .
@@ -835,9 +890,17 @@ The time to wait for one block to be read from an HTTP connection\. If nothing i
 .TP
 \fIDefault\fR:
 
+.
+.SS "http_user_agent"
+The HTTP User\-Agent string to send when making network requests\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: Puppet/5\.0\.0 Ruby/2\.4\.1\-p111 (x86_64\-darwin15)
+.
+.IP "" 0
 .
 .SS "ignorecache"
-Ignore cache and always recompile the configuration\. This is useful for testing new configurations, where the local cache may in fact be stale even if the timestamps are up to date \- if the facts change or if the server changes\.
+This setting has no effect and will be removed in a future Puppet version\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: false
@@ -1016,9 +1079,10 @@ crit
 .SS "logdir"
 The directory in which to store log files
 .
-.TP
-\fIDefault\fR:
-
+.IP "\(bu" 4
+\fIDefault\fR: Unix/Linux: /var/log/puppetlabs/puppet \-\- Windows: C:\eProgramData\ePuppetLabs\epuppet\evar\elog \-\- Non\-root user: ~/\.puppetlabs/var/log
+.
+.IP "" 0
 .
 .SS "manage_internal_file_permissions"
 Whether Puppet should manage the owner, group, and mode of files it uses internally
@@ -1032,7 +1096,7 @@ Whether Puppet should manage the owner, group, and mode of files it uses interna
 The entry\-point manifest for puppet master\. This can be one file or a directory of manifests to be evaluated in alphabetical order\. Puppet manages this path as a directory if one exists or if the path ends with a / or \.
 .
 .P
-Setting a global value for \fBmanifest\fR in puppet\.conf is not allowed (but it can be overridden from them commandline)\. Please use directory environments instead\. If you need to use something other than the environment\'s \fBmanifests\fR directory as the main manifest, you can set \fBmanifest\fR in environment\.conf\. For more info, see https://docs\.puppetlabs\.com/puppet/latest/reference/environments\.html
+Setting a global value for \fBmanifest\fR in puppet\.conf is not allowed (but it can be overridden from the commandline)\. Please use directory environments instead\. If you need to use something other than the environment\'s \fBmanifests\fR directory as the main manifest, you can set \fBmanifest\fR in environment\.conf\. For more info, see \fIhttps://docs\.puppet\.com/puppet/latest/reference/environments\.html\fR
 .
 .TP
 \fIDefault\fR:
@@ -1095,7 +1159,7 @@ Whether to create the necessary user and group that puppet agent will run as\.
 .IP "" 0
 .
 .SS "module_groups"
-Extra module groups to request from the Puppet Forge
+Extra module groups to request from the Puppet Forge\. This is an internal setting, and users should never change it\.
 .
 .TP
 \fIDefault\fR:
@@ -1105,7 +1169,7 @@ Extra module groups to request from the Puppet Forge
 The module repository
 .
 .IP "\(bu" 4
-\fIDefault\fR: https://forgeapi\.puppetlabs\.com
+\fIDefault\fR: https://forgeapi\.puppet\.com
 .
 .IP "" 0
 .
@@ -1129,7 +1193,7 @@ The directory into which module tool data is stored
 The search path for modules, as a list of directories separated by the system path separator character\. (The POSIX path separator is \':\', and the Windows path separator is \';\'\.)
 .
 .P
-Setting a global value for \fBmodulepath\fR in puppet\.conf is not allowed (but it can be overridden from the commandline)\. Please use directory environments instead\. If you need to use something other than the default modulepath of \fB<ACTIVE ENVIRONMENT\'S MODULES DIR>:$basemodulepath\fR, you can set \fBmodulepath\fR in environment\.conf\. For more info, see https://docs\.puppetlabs\.com/puppet/latest/reference/environments\.html
+Setting a global value for \fBmodulepath\fR in puppet\.conf is not allowed (but it can be overridden from the commandline)\. Please use directory environments instead\. If you need to use something other than the default modulepath of \fB<ACTIVE ENVIRONMENT\'S MODULES DIR>:$basemodulepath\fR, you can set \fBmodulepath\fR in environment\.conf\. For more info, see \fIhttps://docs\.puppet\.com/puppet/latest/reference/environments\.html\fR
 .
 .SS "name"
 The name of the application, if we are running as one\. The default is essentially $0 without the path or \fB\.rb\fR\.
@@ -1139,7 +1203,7 @@ The name of the application, if we are running as one\. The default is essential
 
 .
 .SS "node_cache_terminus"
-How to store cached nodes\. Valid values are (none), \'json\', \'msgpack\', \'yaml\' or write only yaml (\'write_only_yaml\')\. The master application defaults to \'write_only_yaml\', all others to none\.
+How to store cached nodes\. Valid values are (none), \'json\', \'msgpack\', \'yaml\' or write only yaml (\'write_only_yaml\')\.
 .
 .TP
 \fIDefault\fR:
@@ -1154,10 +1218,10 @@ How the puppet master determines the client\'s identity and sets the \'hostname\
 .IP "" 0
 .
 .SS "node_name_fact"
-The fact name used to determine the node name used for all requests the agent makes to the master\. WARNING: This setting is mutually exclusive with node_name_value\. Changing this setting also requires changes to the default auth\.conf configuration on the Puppet Master\. Please see http://links\.puppetlabs\.com/node_name_fact for more information\.
+The fact name used to determine the node name used for all requests the agent makes to the master\. WARNING: This setting is mutually exclusive with node_name_value\. Changing this setting also requires changes to the default auth\.conf configuration on the Puppet Master\. Please see http://links\.puppet\.com/node_name_fact for more information\.
 .
 .SS "node_name_value"
-The explicit value used for the node name for all requests the agent makes to the master\. WARNING: This setting is mutually exclusive with node_name_fact\. Changing this setting also requires changes to the default auth\.conf configuration on the Puppet Master\. Please see http://links\.puppetlabs\.com/node_name_value for more information\.
+The explicit value used for the node name for all requests the agent makes to the master\. WARNING: This setting is mutually exclusive with node_name_fact\. Changing this setting also requires changes to the default auth\.conf configuration on the Puppet Master\. Please see http://links\.puppet\.com/node_name_value for more information\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: $certname
@@ -1165,7 +1229,33 @@ The explicit value used for the node name for all requests the agent makes to th
 .IP "" 0
 .
 .SS "node_terminus"
-Where to find information about nodes\.
+Which node data plugin to use when compiling node catalogs\.
+.
+.P
+When Puppet compiles a catalog, it combines two primary sources of info: the main manifest, and a node data plugin (often called a "node terminus," for historical reasons)\. Node data plugins provide three things for a given node name:
+.
+.IP "1." 4
+A list of classes to add to that node\'s catalog (and, optionally, values for their parameters)\.
+.
+.IP "2." 4
+Which Puppet environment the node should use\.
+.
+.IP "3." 4
+A list of additional top\-scope variables to set\.
+.
+.IP "" 0
+.
+.P
+The three main node data plugins are:
+.
+.IP "\(bu" 4
+\fBplain\fR \-\-\- Returns no data, so that the main manifest controls all node configuration\.
+.
+.IP "\(bu" 4
+\fBexec\fR \-\-\- Uses an external node classifier (ENC) \fIhttps://docs\.puppet\.com/puppet/latest/nodes_external\.html\fR, configured by the \fBexternal_nodes\fR setting\. This lets you pull a list of Puppet classes from any external system, using a small glue script to perform the request and format the result as YAML\.
+.
+.IP "\(bu" 4
+\fBclassifier\fR (formerly \fBconsole\fR) \-\-\- Specific to Puppet Enterprise\. Uses the PE console for node data\."
 .
 .IP "\(bu" 4
 \fIDefault\fR: plain
@@ -1179,7 +1269,7 @@ Whether to apply catalogs in noop mode, which allows Puppet to partially simulat
 When running in noop mode, Puppet will check whether each resource is in sync, like it does when running normally\. However, if a resource attribute is not in the desired state (as declared in the catalog), Puppet will take no action, and will instead report the changes it \fIwould\fR have made\. These simulated changes will appear in the report sent to the puppet master, or be shown on the console if running puppet agent or puppet apply in the foreground\. The simulated changes will not send refresh events to any subscribing or notified resources, although Puppet will log that a refresh event \fIwould\fR have been sent\.
 .
 .P
-\fBImportant note:\fR The \fBnoop\fR metaparameter \fIhttps://docs\.puppetlabs\.com/references/latest/metaparameter\.html#noop\fR allows you to apply individual resources in noop mode, and will override the global value of the \fBnoop\fR setting\. This means a resource with \fBnoop => false\fR \fIwill\fR be changed if necessary, even when running puppet agent with \fBnoop = true\fR or \fB\-\-noop\fR\. (Conversely, a resource with \fBnoop => true\fR will only be simulated, even when noop mode is globally disabled\.)
+\fBImportant note:\fR The \fBnoop\fR metaparameter \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/metaparameter\.html#noop\fR allows you to apply individual resources in noop mode, and will override the global value of the \fBnoop\fR setting\. This means a resource with \fBnoop => false\fR \fIwill\fR be changed if necessary, even when running puppet agent with \fBnoop = true\fR or \fB\-\-noop\fR\. (Conversely, a resource with \fBnoop => true\fR will only be simulated, even when noop mode is globally disabled\.)
 .
 .IP "\(bu" 4
 \fIDefault\fR: false
@@ -1284,7 +1374,7 @@ From where to retrieve plugins\. The standard Puppet \fBfile\fR type is used for
 .IP "" 0
 .
 .SS "pluginsync"
-Whether plugins should be synced with the central server\.
+Whether plugins should be synced with the central server\. This setting is deprecated\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: true
@@ -1298,7 +1388,7 @@ A command to run after every agent run\. If this command returns a non\-zero ret
 The preferred means of serializing ruby instances for passing over the wire\. This won\'t guarantee that all instances will be serialized using this method, since not all classes can be guaranteed to support this format, but it will be used for all classes that support it\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: pson
+\fIDefault\fR: json
 .
 .IP "" 0
 .
@@ -1359,7 +1449,7 @@ The fallback log file\. This is only used when the \fB\-\-logdest\fR option is n
 Despite the name, both puppet agent and puppet master will use this file as the fallback logging destination\.
 .
 .P
-For control over logging destinations, see the \fB\-\-logdest\fR command line option in the manual pages for puppet master, puppet agent, and puppet apply\. You can see man pages by running \fBpuppet <SUBCOMMAND> \-\-help\fR, or read them online at https://docs\.puppetlabs\.com/references/latest/man/\.
+For control over logging destinations, see the \fB\-\-logdest\fR command line option in the manual pages for puppet master, puppet agent, and puppet apply\. You can see man pages by running \fBpuppet <SUBCOMMAND> \-\-help\fR, or read them online at https://docs\.puppetlabs\.com/puppet/latest/reference/man/\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: $logdir/puppetd\.log
@@ -1444,6 +1534,14 @@ The configuration file that defines the rights to the different rest indirection
 .
 .IP "" 0
 .
+.SS "rich_data"
+Enables having extended data in the catalog by storing them as a hash with the special key \fB__pcore_type__\fR\. When enabled, resource containing values of the data types \fBBinary\fR, \fBRegexp\fR, \fBSemVer\fR, \fBSemVerRange\fR, \fBTimespan\fR and \fBTimestamp\fR, as well as instances of types derived from \fBObject\fR retain their data type\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: false
+.
+.IP "" 0
+.
 .SS "route_file"
 The YAML file containing indirector route configuration\.
 .
@@ -1455,9 +1553,10 @@ The YAML file containing indirector route configuration\.
 .SS "rundir"
 Where Puppet PID files are kept\.
 .
-.TP
-\fIDefault\fR:
-
+.IP "\(bu" 4
+\fIDefault\fR: Unix/Linux: /var/run/puppetlabs \-\- Windows: C:\eProgramData\ePuppetLabs\epuppet\evar\erun \-\- Non\-root user: ~/\.puppetlabs/var/run
+.
+.IP "" 0
 .
 .SS "runinterval"
 How often puppet agent applies the catalog\. Note that a runinterval of 0 means "run continuously" rather than "never run\." If you want puppet agent to never run, you should start it with the \fB\-\-no\-client\fR option\. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y)\.
@@ -1491,6 +1590,14 @@ The directory in which serialized data is stored, usually in a subdirectory\.
 .
 .IP "" 0
 .
+.SS "server_list"
+The list of puppet master servers to which the puppet agent should connect, in the order that they will be tried\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: []
+.
+.IP "" 0
+.
 .SS "show_diff"
 Whether to log and report a contextual diff when files are being replaced\. This causes partial file contents to pass through Puppet\'s normal logging and reporting system, so this setting should be used with caution if you are sending Puppet\'s reports to an insecure destination\. This feature currently requires the \fBdiff/lcs\fR Ruby library\.
 .
@@ -1507,9 +1614,15 @@ Where the CA stores signed certificates\.
 .
 .IP "" 0
 .
+.SS "skip_tags"
+Tags to use to filter resources\. If this is set, then only resources not tagged with the specified tags will be applied\. Values must be comma\-separated\.
+.
 .SS "splay"
 Whether to sleep for a pseudo\-random (but consistent) amount of time before a run\.
 .
+.P
+For example, without \fBsplay\fR enabled, your agent checks in every 30 minutes at :01 and :31 past the hour\. After enabling \fBsplay\fR, the agent will wait the pseudorandom sleep time, say eight minutes, and then check in every 30 minutes, at :09 and :39 after the hour\. If you restart the same agent at 12:45 PM, it will wait its eight minutes, and check in at 12:52 PM, and every 30 minutes after that, at 1:22 PM, 1:52 PM, and so on\. Other agents will have different sleep times, and so will check in at different times even if they are all restarted at the same time\.
+.
 .IP "\(bu" 4
 \fIDefault\fR: false
 .
@@ -1542,7 +1655,7 @@ Certificate authorities who issue server certificates\. SSL servers will not be
 The header containing an authenticated client\'s SSL DN\. This header must be set by the proxy to the authenticated client\'s SSL DN (e\.g\., \fB/CN=puppet\.puppetlabs\.com\fR)\. Puppet will parse out the Common Name (CN) from the Distinguished Name (DN) and use the value of the CN field for authorization\.
 .
 .P
-Note that the name of the HTTP header gets munged by the web server common gateway inteface: an \fBHTTP_\fR prefix is added, dashes are converted to underscores, and all letters are uppercased\. Thus, to use the \fBX\-Client\-DN\fR header, this setting should be \fBHTTP_X_CLIENT_DN\fR\.
+Note that the name of the HTTP header gets munged by the web server common gateway interface: an \fBHTTP_\fR prefix is added, dashes are converted to underscores, and all letters are uppercased\. Thus, to use the \fBX\-Client\-DN\fR header, this setting should be \fBHTTP_X_CLIENT_DN\fR\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: HTTP_X_CLIENT_DN
@@ -1553,7 +1666,7 @@ Note that the name of the HTTP header gets munged by the web server common gatew
 The header containing the status message of the client verification\. This header must be set by the proxy to \'SUCCESS\' if the client successfully authenticated, and anything else otherwise\.
 .
 .P
-Note that the name of the HTTP header gets munged by the web server common gateway inteface: an \fBHTTP_\fR prefix is added, dashes are converted to underscores, and all letters are uppercased\. Thus, to use the \fBX\-Client\-Verify\fR header, this setting should be \fBHTTP_X_CLIENT_VERIFY\fR\.
+Note that the name of the HTTP header gets munged by the web server common gateway interface: an \fBHTTP_\fR prefix is added, dashes are converted to underscores, and all letters are uppercased\. Thus, to use the \fBX\-Client\-Verify\fR header, this setting should be \fBHTTP_X_CLIENT_VERIFY\fR\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: HTTP_X_CLIENT_VERIFY
@@ -1591,6 +1704,14 @@ Where puppet agent and puppet master store state associated with the running con
 .
 .IP "" 0
 .
+.SS "static_catalogs"
+Whether to compile a static catalog\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: true
+.
+.IP "" 0
+.
 .SS "storeconfigs"
 Whether to store each client\'s configuration, including catalogs, facts, and related data\. This also enables the import and export of resources in the Puppet language \- a mechanism for exchange resources between nodes\.
 .
@@ -1613,6 +1734,39 @@ Configure the backend terminus used for StoreConfigs\. By default, this uses the
 .
 .IP "" 0
 .
+.SS "strict"
+The strictness level of puppet\. Allowed values are:
+.
+.IP "\(bu" 4
+off \- do not perform extra validation, do not report
+.
+.IP "\(bu" 4
+warning \- perform extra validation, report as warning (default)
+.
+.IP "\(bu" 4
+error \- perform extra validation, fail with error
+.
+.IP "" 0
+.
+.P
+The strictness level is for both language semantics and runtime evaluation validation\. In addition to controlling the behavior with this master switch some individual warnings may also be controlled by the disable_warnings setting\.
+.
+.P
+No new validations will be added to a micro (x\.y\.z) release, but may be added in minor releases (x\.y\.0)\. In major releases it expected that most (if not all) strictness validation become standard behavior\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: warning
+.
+.IP "" 0
+.
+.SS "strict_environment_mode"
+Whether the agent specified environment should be considered authoritative, causing the run to fail if the retrieved catalog does not match it\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: false
+.
+.IP "" 0
+.
 .SS "strict_hostname_checking"
 Whether to only search for the complete hostname as it is in the certificate when searching for node information in the catalogs\.
 .
@@ -1622,7 +1776,7 @@ Whether to only search for the complete hostname as it is in the certificate whe
 .IP "" 0
 .
 .SS "strict_variables"
-Makes the parser raise errors when referencing unknown variables\. (This does not affect referencing variables that are explicitly set to undef)\.
+Causes an evaluation error when referencing unknown variables\. (This does not affect referencing variables that are explicitly set to undef)\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: false
@@ -1637,6 +1791,14 @@ Whether to print a transaction summary\.
 .
 .IP "" 0
 .
+.SS "supported_checksum_types"
+Checksum types supported by this agent for use in file resources of a static catalog\. Values must be comma\-separated\. Valid types are md5, md5lite, sha256, sha256lite, sha1, sha1lite, mtime, ctime\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: ["md5", "sha256"]
+.
+.IP "" 0
+.
 .SS "syslogfacility"
 What syslog facility to use when logging to syslog\. Syslog has a fixed list of valid facilities, and you must choose one of those; you cannot just make one up\.
 .
@@ -1656,6 +1818,14 @@ Whether to print stack traces on some errors
 .
 .IP "" 0
 .
+.SS "transactionstorefile"
+Transactional storage file for persisting data between transactions for the purposes of infering information (such as corrective_change) on new data received\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: $statedir/transactionstore\.yaml
+.
+.IP "" 0
+.
 .SS "trusted_oid_mapping_file"
 File that provides mapping between custom SSL oids and user\-friendly names
 .
@@ -1665,10 +1835,10 @@ File that provides mapping between custom SSL oids and user\-friendly names
 .IP "" 0
 .
 .SS "trusted_server_facts"
-Stores a trusted set of server\-side global variables in a hash called $server_facts, which cannot be cannot be overridden by client_facts or logic in manifests\. Makes it illegal to assign to the variable $server_facts in any scope\.
+The \'trusted_server_facts\' setting is deprecated and has no effect as the feature this enabled is now always on\. The setting will be removed in a future version of puppet\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: false
+\fIDefault\fR: true
 .
 .IP "" 0
 .
@@ -1708,7 +1878,7 @@ The user puppet master should run as\.
 Where Puppet stores dynamic and growing data\. The default for this setting is calculated specially, like \fBconfdir\fR_\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: /opt/puppetlabs/puppet/cache
+\fIDefault\fR: Unix/Linux: /opt/puppetlabs/puppet/cache \-\- Windows: C:\eProgramData\ePuppetLabs\epuppet\ecache \-\- Non\-root user: ~/\.puppetlabs/opt/puppet/cache
 .
 .IP "" 0
 .
@@ -1735,4 +1905,4 @@ The directory in which YAML data is stored, usually in a subdirectory\.
 .IP "" 0
 .
 .P
-\fIThis page autogenerated on 2015\-05\-18 10:15:47 \-0700\fR
+\fIThis page autogenerated on 2017\-06\-29 14:42:23 \-0700\fR