Open source Puppet 6.11

  1. Configuration settings
    1. agent_catalog_run_lockfile
    2. agent_disabled_lockfile
    3. allow_duplicate_certs
    4. always_retry_plugins
    5. autoflush
    6. autosign
    7. basemodulepath
    8. binder_config
    9. bucketdir
    10. ca_fingerprint
    11. ca_name
    12. ca_port
    13. ca_server
    14. ca_ttl
    15. cacert
    16. cacrl
    17. cadir
    18. cakey
    19. capub
    20. catalog_cache_terminus
    21. catalog_terminus
    22. cert_inventory
    23. certdir
    24. certificate_revocation
    25. certname
    26. classfile
    27. client_datadir
    28. clientbucketdir
    29. clientyamldir
    30. code
    31. codedir
    32. color
    33. confdir
    34. config
    35. config_file_name
    36. config_version
    37. configprint
    38. crl_refresh_interval
    39. csr_attributes
    40. csrdir
    41. daemonize
    42. data_binding_terminus
    43. default_file_terminus
    44. default_manifest
    45. default_schedules
    46. deviceconfdir
    47. deviceconfig
    48. devicedir
    49. diff
    50. diff_args
    51. digest_algorithm
    52. disable_i18n
    53. disable_per_environment_manifest
    54. disable_warnings
    55. dns_alt_names
    56. document_all
    57. environment
    58. environment_data_provider
    59. environment_timeout
    60. environmentpath
    61. evaltrace
    62. external_nodes
    63. factpath
    64. facts_terminus
    65. fileserverconfig
    66. filetimeout
    67. forge_authorization
    68. freeze_main
    69. func3x_check
    70. future_features
    71. genconfig
    72. genmanifest
    73. graph
    74. graphdir
    75. group
    76. hiera_config
    77. hostcert
    78. hostcrl
    79. hostcsr
    80. hostprivkey
    81. hostpubkey
    82. http_connect_timeout
    83. http_debug
    84. http_keepalive_timeout
    85. http_proxy_host
    86. http_proxy_password
    87. http_proxy_port
    88. http_proxy_user
    89. http_read_timeout
    90. http_user_agent
    91. ignoremissingtypes
    92. ignoreschedules
    93. key_type
    94. keylength
    95. lastrunfile
    96. lastrunreport
    97. ldapattrs
    98. ldapbase
    99. ldapclassattrs
    100. ldapparentattr
    101. ldappassword
    102. ldapport
    103. ldapserver
    104. ldapssl
    105. ldapstackedattrs
    106. ldapstring
    107. ldaptls
    108. ldapuser
    109. libdir
    110. localcacert
    111. localedest
    112. localesource
    113. log_level
    114. logdest
    115. logdir
    116. manage_internal_file_permissions
    117. manifest
    118. masterport
    119. max_deprecations
    120. max_errors
    121. max_warnings
    122. maximum_uid
    123. maxwaitforcert
    124. mkusers
    125. module_groups
    126. module_repository
    127. module_working_dir
    128. modulepath
    129. name
    130. named_curve
    131. no_proxy
    132. node_cache_terminus
    133. node_name
    134. node_name_fact
    135. node_name_value
    136. node_terminus
    137. noop
    138. onetime
    139. passfile
    140. path
    141. pidfile
    142. plugindest
    143. pluginfactdest
    144. pluginfactsource
    145. pluginsignore
    146. pluginsource
    147. postrun_command
    148. preferred_serialization_format
    149. prerun_command
    150. preview_outputdir
    151. priority
    152. privatedir
    153. privatekeydir
    154. profile
    155. publickeydir
    156. puppetdlog
    157. report
    158. report_port
    159. report_server
    160. reportdir
    161. reports
    162. reporturl
    163. requestdir
    164. resourcefile
    165. rest_authconfig
    166. rich_data
    167. route_file
    168. rundir
    169. runinterval
    170. runtimeout
    171. serial
    172. server
    173. server_datadir
    174. server_list
    175. show_diff
    176. signeddir
    177. skip_tags
    178. sourceaddress
    179. splay
    180. splaylimit
    181. srv_domain
    182. ssl_client_ca_auth
    183. ssl_client_header
    184. ssl_client_verify_header
    185. ssl_lockfile
    186. ssl_server_ca_auth
    187. ssldir
    188. statedir
    189. statefile
    190. statettl
    191. static_catalogs
    192. storeconfigs
    193. storeconfigs_backend
    194. strict
    195. strict_environment_mode
    196. strict_hostname_checking
    197. strict_variables
    198. summarize
    199. supported_checksum_types
    200. syslogfacility
    201. tags
    202. tasks
    203. trace
    204. transactionstorefile
    205. trusted_oid_mapping_file
    206. use_cached_catalog
    207. use_srv_records
    208. usecacheonfailure
    209. user
    210. vardir
    211. vendormoduledir
    212. waitforcert
    213. yamldir

This page is autogenerated; any changes will get overwritten

Configuration settings

  • Each of these settings can be specified in puppet.conf or on the command line.
  • Puppet Enterprise (PE) and open source Puppet share the configuration settings that are documented here. However, PE defaults for some settings differ from the open source Puppet defaults. Some examples of settings that have different PE defaults include disable18n, environment_timeout, always_retry_plugins, and the Puppet Server JRuby max-active-instances setting. To verify PE configuration defaults, check the puppet.conf file after installation.
  • When using boolean settings on the command line, use --setting and --no-setting instead of --setting (true|false). (Using --setting false results in “Error: Could not parse application options: needless argument”.)
  • Settings can be interpolated as $variables in other settings; $environment is special, in that puppet master will interpolate each agent node’s environment instead of its own.
  • Multiple values should be specified as comma-separated lists; multiple directories should be separated with the system path separator (usually a colon).
  • Settings that represent time intervals should be specified in duration format: an integer immediately followed by one of the units ‘y’ (years of 365 days), ‘d’ (days), ‘h’ (hours), ‘m’ (minutes), or ‘s’ (seconds). The unit cannot be combined with other units, and defaults to seconds when omitted. Examples are ‘3600’ which is equivalent to ‘1h’ (one hour), and ‘1825d’ which is equivalent to ‘5y’ (5 years).
  • If you use the splay setting, note that the period that it waits changes each time the Puppet agent is restarted.
  • Settings that take a single file or directory can optionally set the owner, group, and mode for their value: rundir = $vardir/run { owner = puppet, group = puppet, mode = 644 }
  • The Puppet executables ignores any setting that isn’t relevant to their function.

See the configuration guide for more details.


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.

  • Default: $statedir/agent_catalog_run.lock


A lock file to indicate that puppet agent runs have been administratively disabled. File contains a JSON object with state information.

  • Default: $statedir/agent_disabled.lock


Whether to allow a new certificate request to overwrite an existing certificate request. If true, then the old certificate must be cleaned using puppetserver ca clean, and the new request signed using puppetserver ca sign.

  • Default: false


Affects how we cache attempts to load Puppet resource types and features. If true, then calls to Puppet.type.<type>? Puppet.feature.<feature>? 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).

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.

  • Default: true


Whether log files should always flush to disk.

  • Default: true


Whether (and how) to autosign certificate requests. This setting is only relevant on a puppet master acting as a certificate authority (CA).

Valid values are true (autosigns all certificate requests; not recommended), false (disables autosigning certificates), or the absolute path to a file.

The file specified in this setting may be either a configuration file or a custom policy executable. Puppet will automatically determine what it is: If the Puppet user (see the user setting) can execute the file, it will be treated as a policy executable; otherwise, it will be treated as a config file.

If a custom policy executable is configured, the CA puppet master will run it every time it receives a CSR. The executable will be passed the subject CN of the request as a command line argument, and the contents of the CSR in PEM format on stdin. It should exit with a status of 0 if the cert should be autosigned and non-zero if the cert should not be autosigned.

If a certificate request is not autosigned, it will persist for review. An admin user can use the puppetserver ca sign command to manually sign it, or can delete the request.

For info on autosign configuration files, see the guide to Puppet’s config files.

  • Default: $confdir/autosign.conf


The search path for global 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 ‘;’.)

These are the modules that will be used by all environments. Note that the modules directory of the active environment will have priority over any global directories. For more info, see

  • Default: $codedir/modules:/opt/puppetlabs/puppet/modules


The binder configuration file. Puppet reads this file on each request to configure the bindings system. If set to nil (the default), a $confdir/binder_config.yaml is optionally loaded. If it does not exists, a default configuration is used. If the setting :binding_config is specified, it must reference a valid and existing yaml file.

  • Default:


Where FileBucket files are stored.

  • Default: $vardir/bucket


The expected fingerprint of the CA certificate. If specified, the agent will compare the CA certificate fingerprint that it downloads against this value and reject the CA certificate if the values do not match. This only applies during the first download of the CA certificate.

  • Default:


The name to use the Certificate Authority certificate.

  • Default: Puppet CA: $certname


The port to use for the certificate authority.

  • Default: $masterport


The server to use for certificate authority requests. It’s a separate server because it cannot and does not need to horizontally scale.

  • Default: $server


The default TTL for new certificates. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: 5y


The CA certificate.

  • Default: $cadir/ca_crt.pem


The certificate revocation list (CRL) for the CA.

  • Default: $cadir/ca_crl.pem


The root directory for the certificate authority.

  • Default: $ssldir/ca


The CA private key.

  • Default: $cadir/ca_key.pem


The CA public key.

  • Default: $cadir/ca_pub.pem


How to store cached catalogs. Valid values are ‘json’, ‘msgpack’ and ‘yaml’. The agent application defaults to ‘json’.

  • Default:


Where to get node catalogs. This is useful to change if, for instance, you’d like to pre-compile catalogs and store them in memcached or some other easily-accessed store.

  • Default: compiler


The inventory file. This is a text file to which the CA writes a complete listing of all certificates.

  • Default: $cadir/inventory.txt


The certificate directory.

  • Default: $ssldir/certs


Whether certificate revocation checking should be enabled, and what level of checking should be performed.

When certificate revocation is enabled, Puppet expects the contents of its CRL to be one or more PEM-encoded CRLs concatenated together. When using a cert bundle, CRLs for all CAs in the chain of trust must be included in the crl file. The chain should be ordered from least to most authoritative, with the first CRL listed being for the root of the chain and the last being for the leaf CA.

When certificate_revocation is set to ‘true’ or ‘chain’, Puppet ensures that each CA in the chain of trust has not been revoked by its issuing CA.

When certificate_revocation is set to ‘leaf’, Puppet verifies certs against the issuing CA’s revocation list, but it does not verify the revocation status of the issuing CA or any CA above it within the chain of trust.

When certificate_revocation is set to ‘false’, Puppet disables all certificate revocation checking and does not attempt to download the CRL.

  • Default: chain


The name to use when handling certificates. When a node requests a certificate from the CA puppet master, it uses the value of the certname setting as its requested Subject CN.

This is the name used when managing a node’s permissions in auth.conf. In most cases, it is also used as the node’s name when matching node definitions and requesting data from an ENC. (This can be changed with the node_name_value and node_name_fact settings, although you should only do so if you have a compelling reason.)

A node’s certname is available in Puppet manifests as $trusted['certname']. (See Facts and Built-In Variables for more details.)

  • For best compatibility, you should limit the value of certname to only use lowercase letters, numbers, periods, underscores, and dashes. (That is, it should match /A[a-z0-9._-]+Z/.)
  • The special value ca is reserved, and can’t be used as the certname for a normal node.

Defaults to the node’s fully qualified domain name.

  • Default: the Host’s fully qualified domain name, as determined by Facter


The file in which puppet agent stores a list of the classes associated with the retrieved configuration. Can be loaded in the separate puppet executable using the --loadclasses option.

  • Default: $statedir/classes.txt


The directory in which serialized data is stored on the client.

  • Default: $vardir/client_data


Where FileBucket files are stored locally.

  • Default: $vardir/clientbucket


The directory in which client-side YAML data is stored.

  • Default: $vardir/client_yaml


Code to parse directly. This is essentially only used by puppet, and should only be set if you’re writing your own Puppet executable.


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.

  • Default: Unix/Linux: /etc/puppetlabs/code – Windows: C:\ProgramData\PuppetLabs\code – Non-root user: ~/.puppetlabs/etc/code


Whether to use colors when logging to the console. Valid values are ansi (equivalent to true), html, and false, which produces no color. Defaults to false on Windows, as its console does not support ansi colors.

  • Default: ansi


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.

  • Default: Unix/Linux: /etc/puppetlabs/puppet – Windows: C:\ProgramData\PuppetLabs\puppet\etc – Non-root user: ~/.puppetlabs/etc/puppet


The configuration file for the current puppet application.

  • Default: $confdir/${config_file_name}


The name of the puppet config file.

  • Default: puppet.conf


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.

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


Prints 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’. This setting is deprecated, the ‘puppet config’ command replaces this functionality.


How often the Puppet agent refreshes its local CRL. By default the CRL is only downloaded once, and never refreshed. If a duration is specified, then the agent will refresh its CRL whenever it next runs and the elapsed time since the CRL was last refreshed exceeds the duration.

In general, the duration should be greater than the runinterval. Setting it to an equal or lesser value will cause the CRL to be refreshed on every run.

If the agent downloads a new CRL, the agent will use it for subsequent network requests. If the refresh request fails or if the CRL is unchanged on the server, then the agent run will continue using the local CRL it already has.This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default:


An optional file containing custom attributes to add to certificate signing requests (CSRs). You should ensure that this file does not exist on your CA puppet master; if it does, unwanted certificate extensions may leak into certificates created with the puppetserver ca generate command.

If present, this file must be a YAML hash containing a custom_attributes key and/or an extension_requests key. The value of each key must be a hash, where each key is a valid OID and each value is an object that can be cast to a string.

Custom attributes can be used by the CA when deciding whether to sign the certificate, but are then discarded. Attribute OIDs can be any OID value except the standard CSR attributes (i.e. attributes described in RFC 2985 section 5.4). This is useful for embedding a pre-shared key for autosigning policy executables (see the autosign setting), often by using the 1.2.840.113549.1.9.7 (“challenge password”) OID.

Extension requests will be permanently embedded in the final certificate. Extension OIDs must be in the “ppRegCertExt” ( or “ppPrivCertExt” ( OID arcs. The ppRegCertExt arc is reserved for four of the most common pieces of data to embed: pp_uuid (.1), pp_instance_id (.2), pp_image_name (.3), and pp_preshared_key (.4) — in the YAML file, these can be referred to by their short descriptive names instead of their full OID. The ppPrivCertExt arc is unregulated, and can be used for site-specific extensions.

  • Default: $confdir/csr_attributes.yaml


Where the CA stores certificate requests.

  • Default: $cadir/requests


Whether to send the process into the background. This defaults to true on POSIX systems, and to false on Windows (where Puppet currently cannot daemonize).

  • Default: true


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.

  • Default: hiera


The default source for files if no server is given in a uri, e.g. puppet:///file. The default of rest causes the file to be retrieved using the server setting. When running apply the default is file_server, causing requests to be filled locally.

  • Default: rest


The default main manifest for directory environments. Any environment that doesn’t set the manifest setting in its environment.conf file will use this manifest.

This setting’s value can be an absolute or relative path. An absolute path will make all environments default to the same main manifest; a relative path will allow each environment to use its own manifest, and Puppet will resolve the path relative to each environment’s main directory.

In either case, the path can point to a single file or to a directory of manifests to be evaluated in alphabetical order.

  • Default: ./manifests


Boolean; whether to generate the default schedule resources. Setting this to false is useful for keeping external report processors clean of skipped schedule resources.

  • Default: true


The root directory of devices’ $confdir.

  • Default: $confdir/devices


Path to the device config file for puppet device.

  • Default: $confdir/device.conf


The root directory of devices’ $vardir.

  • Default: $vardir/devices


Which diff command to use when printing differences between files. This setting has no default value on Windows, as standard diff is not available, but Puppet can use many third-party diff tools.

  • Default: diff


Which arguments to pass to the diff command when printing differences between files. The command to use can be chosen with the diff setting.

  • Default: -u


Which digest algorithm to use for file resources and the filebucket. Valid values are md5, sha256, sha384, sha512, sha224. Default is md5.

  • Default: md5


If true, turns off all translations of Puppet and module log messages, which affects error, warning, and info log messages, as well as any translations in the report and CLI.

  • Default: false


Whether to disallow an environment-specific main manifest. When set to true, Puppet will use the manifest specified in the default_manifest setting for all environments. If an environment specifies a different main manifest in its environment.conf file, catalog requests for that environment will fail with an error.

This setting requires default_manifest to be set to an absolute path.

  • Default: false


A comma-separated list of warning types to suppress. If large numbers of warnings are making Puppet’s logs too large or difficult to use, you can temporarily silence them with this setting.

If you are preparing to upgrade Puppet to a new major version, you should re-enable all warnings for a while.

Valid values for this setting are:

  • deprecations — disables deprecation warnings.
  • undefined_variables — disables warnings about non existing variables.
  • undefined_resources — disables warnings about non existing resources.

  • Default: []


A comma-separated list of alternate DNS names for Puppet Server. These are extra hostnames (in addition to its certname) that the server is allowed to use when serving agents. Puppet checks this setting when automatically creating a certificate for Puppet agent or Puppet Server. These can be either IP or DNS, and the type should be specified and followed with a colon. Untyped inputs will default to DNS.

In order to handle agent requests at a given hostname (like “”), 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.

Note: 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 regenerate the certificate. For more information on that process, see the [cert regen docs] (

To see all the alternate names your servers are using, log into your CA server and run puppetserver ca list --all, then check the output for (alt names: ...). 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.


Whether to document all resources when using puppet doc to generate manifest documentation.

  • Default: false


The environment in which Puppet is running. For clients, such as puppet agent, this determines the environment itself, which Puppet uses to find modules and much more. For servers, such as puppet master, this provides the default environment for nodes that Puppet knows nothing about.

When defining an environment in the [agent] section, this refers to the environment that the agent requests from the master. The environment doesn’t have to exist on the local filesystem because the agent fetches it from the master. This definition is used when running puppet agent.

When defined in the [user] section, the environment refers to the path that Puppet uses to search for code and modules related to its execution. This requires the environment to exist locally on the filesystem where puppet is being executed. Puppet subcommands, including puppet module and puppet apply, use this definition.

Given that the context and effects vary depending on the config section in which the environment setting is defined, do not set it globally.

  • Default: production


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.

  • Default:


How long the Puppet master should cache data it loads from an environment.

A value of 0 will disable caching. This setting can also be set to unlimited, which will cache environments until the master is restarted or told to refresh the cache.

You should change this setting once your Puppet deployment is doing non-trivial work. We chose the default value of 0 because it lets new users update their code without any extra steps, but it lowers the performance of your Puppet master.

We recommend setting this to unlimited and explicitly refreshing your Puppet master as part of your code deployment process.

  • With Puppet Server, you should refresh environments by calling the environment-cache API endpoint. See the docs for the Puppet Server administrative API.

Any value other than 0 or unlimited is deprecated, since most Puppet servers use a pool of Ruby interpreters which all have their own cache timers. When these timers drift out of sync, agents can be served inconsistent catalogs.

  • Default: 0


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 ‘;’.)

This setting must have a value set to enable directory environments. The recommended value is $codedir/environments. For more details, see

  • Default: $codedir/environments


Whether each resource should log when it is being evaluated. This allows you to interactively see exactly what is being done.

  • Default: false


The external node classifier (ENC) script to use for node data. Puppet combines this data with the main manifest to produce node catalogs.

To enable this setting, set the node_terminus setting to exec.

This setting’s value must be the path to an executable command that can produce node information. The command must:

  • Take the name of a node as a command-line argument.
  • Return a YAML hash with up to three keys:
    • classes — A list of classes, as an array or hash.
    • environment — A string.
    • parameters — A list of top-scope variables to set, as a hash.
  • For unknown nodes, exit with a non-zero exit code.

Generally, an ENC script makes requests to an external data source.

For more info, see the ENC documentation.

  • Default: none


Where Puppet should look for facts. Multiple directories should be separated by the system path separator character. (The POSIX path separator is ‘:’, and the Windows path separator is ‘;’.)

  • Default: $vardir/lib/facter:$vardir/facts


The node facts terminus.

  • Default: facter


Where the fileserver configuration is stored.

  • Default: $confdir/fileserver.conf


The minimum time to wait between checking for updates in configuration files. This timeout determines how quickly Puppet checks whether a file (such as manifests or puppet.conf) has changed on disk. The default will change in a future release to be ‘unlimited’, requiring a reload of the Puppet service to pick up changes to its internal configuration. Currently we do not accept a value of ‘unlimited’. To reparse files within an environment in Puppet Server please use the environment_cache endpoint

  • Default: 15s


The authorization key to connect to the Puppet Forge. Leave blank for unauthorized or license based connections

  • Default:


Freezes the ‘main’ class, disallowing any code to be added to it. This essentially means that you can’t have any code outside of a node, class, or definition other than in the site manifest.

  • Default: false


Causes validation of loaded legacy Ruby functions (3x API) to raise errors about illegal constructs that could cause harm or that simply does not work. This flag is on by default. This flag is made available so that the validation can be turned off in case the method of validation is faulty - if encountered, please file a bug report.

  • Default: true


Whether or not to enable all features currently being developed for future major releases of Puppet. Should be used with caution, as in development features are experimental and can have unexpected effects.

  • Default: false


When true, causes Puppet applications to print an example config file to stdout and exit. The example will include descriptions of each setting, and the current (or default) value of each setting, incorporating any settings overridden on the CLI (with the exception of genconfig itself). This setting only makes sense when specified on the command line as --genconfig.

  • Default: false


Whether to just print a manifest to stdout and exit. Only makes sense when specified on the command line as --genmanifest. Takes into account arguments specified on the CLI.

  • Default: false


Whether to create .dot graph files, which let you visualize the dependency and containment relationships in Puppet’s catalog. You can load and view these files with tools like OmniGraffle (OS X) or graphviz (multi-platform).

Graph files are created when applying a catalog, so this setting should be used on nodes running puppet agent or puppet apply.

The graphdir setting determines where Puppet will save graphs. Note that we don’t save graphs for historical runs; Puppet will replace the previous .dot files with new ones every time it applies a catalog.

See your graphing software’s documentation for details on opening .dot files. If you’re using GraphViz’s dot command, you can do a quick PNG render with dot -Tpng <DOT FILE> -o <OUTPUT FILE>.

  • Default: false


Where to save .dot-format graphs (when the graph setting is enabled).

  • Default: $statedir/graphs


The group Puppet Server will run as. Used to ensure the agent side processes (agent, apply, etc) create files and directories readable by Puppet Server when necessary.

  • Default: puppet


The hiera configuration file. Puppet only reads this file on startup, so you must restart the puppet master every time you edit it.

  • Default: $confdir/hiera.yaml. However, for backwards compatibility, if a file exists at $codedir/hiera.yaml, Puppet uses that instead.


Where individual hosts store and look for their certificates.

  • Default: $certdir/$certname.pem


Where the host’s certificate revocation list can be found. This is distinct from the certificate authority’s CRL.

  • Default: $ssldir/crl.pem


This setting is deprecated.

  • Default: $ssldir/csr_$certname.pem


Where individual hosts store and look for their private key.

  • Default: $privatekeydir/$certname.pem


Where individual hosts store and look for their public key.

  • Default: $publickeydir/$certname.pem


The maximum amount of time to wait when establishing an HTTP connection. The default value is 2 minutes. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: 2m


Whether to write HTTP request and responses to stderr. This should never be used in a production environment.

  • Default: false


The maximum amount of time a persistent HTTP connection can remain idle in the connection pool, before it is closed. This timeout should be shorter than the keepalive timeout used on the HTTP server, e.g. Apache KeepAliveTimeout directive. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: 4s


The HTTP proxy host to use for outgoing connections. Note: You may need to use a FQDN for the server hostname when using a proxy. Environment variable http_proxy or HTTP_PROXY will override this value

  • Default: none


The password for the user of an authenticated HTTP proxy. Requires the http_proxy_user setting.

Note that passwords must be valid when used as part of a URL. If a password contains any characters with special meanings in URLs (as specified by RFC 3986 section 2.2), they must be URL-encoded. (For example, # would become %23.)

  • Default: none


The HTTP proxy port to use for outgoing connections

  • Default: 3128


The user name for an authenticated HTTP proxy. Requires the http_proxy_host setting.

  • Default: none


The time to wait for data to be read from an HTTP connection. If nothing is read after the elapsed interval then the connection will be closed. The default value is 10 minutes. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: 10m


The HTTP User-Agent string to send when making network requests.

  • Default: Puppet/6.10.1 Ruby/2.5.1-p57 (x86_64-darwin17)


Skip searching for classes and definitions that were missing during a prior compilation. The list of missing objects is maintained per-environment and persists until the environment is cleared or the master is restarted.

  • Default: false


Boolean; whether puppet agent should ignore schedules. This is useful for initial puppet agent runs.

  • Default: false


The type of private key. Valid values are rsa and ec. Default is rsa.

  • Default: rsa


The bit length of keys.

  • Default: 4096


Where puppet agent stores the last run report summary in yaml format.

  • Default: $statedir/last_run_summary.yaml


Where puppet agent stores the last run report in yaml format.

  • Default: $statedir/last_run_report.yaml


The LDAP attributes to include when querying LDAP for nodes. All returned attributes are set as variables in the top-level scope. Multiple values should be comma-separated. The value ‘all’ returns all attributes.

  • Default: all


The search base for LDAP searches. It’s impossible to provide a meaningful default here, although the LDAP libraries might have one already set. Generally, it should be the ‘ou=Hosts’ branch under your main directory.


The LDAP attributes to use to define Puppet classes. Values should be comma-separated.

  • Default: puppetclass


The attribute to use to define the parent node.

  • Default: parentnode


The password to use to connect to LDAP.


The LDAP port.

  • Default: 389


The LDAP server.

  • Default: ldap


Whether SSL should be used when searching for nodes. Defaults to false because SSL usually requires certificates to be set up on the client side.

  • Default: false


The LDAP attributes that should be stacked to arrays by adding the values in all hierarchy elements of the tree. Values should be comma-separated.

  • Default: puppetvar


The search string used to find an LDAP node.

  • Default: (&(objectclass=puppetClient)(cn=%s))


Whether TLS should be used when searching for nodes. Defaults to false because TLS usually requires certificates to be set up on the client side.

  • Default: false


The user to use to connect to LDAP. Must be specified as a full DN.


An extra search path for Puppet. This is only useful for those files that Puppet will load on demand, and is only guaranteed to work for those cases. In fact, the autoload mechanism is responsible for making sure this directory is in Ruby’s search path

  • Default: $vardir/lib


Where each client stores the CA certificate.

  • Default: $certdir/ca.pem


Where Puppet should store translation files that it pulls down from the central server.

  • Default: $vardir/locales


From where to retrieve translation files. The standard Puppet file type is used for retrieval, so anything that is a valid file source can be used here.

  • Default: puppet:///locales


Default logging level for messages from Puppet. Allowed values are:

  • debug
  • info
  • notice
  • warning
  • err
  • alert
  • emerg
  • crit

  • Default: notice


Where to send log messages. Choose between ‘syslog’ (the POSIX syslog service), ‘eventlog’ (the Windows Event Log), ‘console’, or the path to a log file.

  • Default:


The directory in which to store log files

  • Default: Unix/Linux: /var/log/puppetlabs/puppet – Windows: C:\ProgramData\PuppetLabs\puppet\var\log – Non-root user: ~/.puppetlabs/var/log


Whether Puppet should manage the owner, group, and mode of files it uses internally.

Note: For Windows agents, the default is false for versions 4.10.13 and greater, versions 5.5.6 and greater, and versions 6.0 and greater.

  • Default: true


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 .

Setting a global value for manifest 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 manifests directory as the main manifest, you can set manifest in environment.conf. For more info, see

  • Default:


The default port puppet subcommands use to communicate with Puppet Server. (eg puppet facts upload, puppet agent). May be overridden by more specific settings (see ca_port, report_port).

  • Default: 8140


Sets the max number of logged/displayed parser validation deprecation warnings in case multiple deprecation warnings have been detected. A value of 0 blocks the logging of deprecation warnings. The count is per manifest.

  • Default: 10


Sets the max number of logged/displayed parser validation errors in case multiple errors have been detected. A value of 0 is the same as a value of 1; a minimum of one error is always raised. The count is per manifest.

  • Default: 10


Sets the max number of logged/displayed parser validation warnings in case multiple warnings have been detected. A value of 0 blocks logging of warnings. The count is per manifest.

  • Default: 10


The maximum allowed UID. Some platforms use negative UIDs but then ship with tools that do not know how to handle signed ints, so the UIDs show up as huge numbers that can then not be fed back into the system. This is a hackish way to fail in a slightly more useful way when that happens.

  • Default: 4294967290


The maximum amount of time the Puppet agent should wait for its certificate request to be signed. A value of unlimited will cause puppet agent to ask for a signed certificate indefinitely. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: unlimited


Whether to create the necessary user and group that puppet agent will run as.

  • Default: false


Extra module groups to request from the Puppet Forge. This is an internal setting, and users should never change it.

  • Default:


The module repository

  • Default:


The directory into which module tool data is stored

  • Default: $vardir/puppet-module


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 ‘;’.)

Setting a global value for modulepath 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 <ACTIVE ENVIRONMENT'S MODULES DIR>:$basemodulepath, you can set modulepath in environment.conf. For more info, see


The name of the application, if we are running as one. The default is essentially $0 without the path or .rb.

  • Default:


The short name for the EC curve used to generate the EC private key. Valid values must be one of the curves in OpenSSL::PKey::EC.builtin_curves. Default is prime256v1.

  • Default: prime256v1


List of domain names that should not go through http_proxy_host. Environment variable no_proxy or NO_PROXY will override this value.

  • Default: localhost,


How to store cached nodes. Valid values are (none), ‘json’, ‘msgpack’, or ‘yaml’.

  • Default:


How the puppet master determines the client’s identity and sets the ‘hostname’, ‘fqdn’ and ‘domain’ facts for use in the manifest, in particular for determining which ‘node’ statement applies to the client. Possible values are ‘cert’ (use the subject’s CN in the client’s certificate) and ‘facter’ (use the hostname that the client reported in its facts)

  • Default: cert


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 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 for more information.

  • Default: $certname


Which node data plugin to use when compiling node catalogs.

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:

  1. A list of classes to add to that node’s catalog (and, optionally, values for their parameters).
  2. Which Puppet environment the node should use.
  3. A list of additional top-scope variables to set.

The three main node data plugins are:

  • plain — Returns no data, so that the main manifest controls all node configuration.
  • exec — Uses an external node classifier (ENC), configured by the external_nodes 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.
  • classifier (formerly console) — Specific to Puppet Enterprise. Uses the PE console for node data.”

  • Default: plain


Whether to apply catalogs in noop mode, which allows Puppet to partially simulate a normal run. This setting affects puppet agent and puppet apply.

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 would 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 would have been sent.

Important note: The noop metaparameter allows you to apply individual resources in noop mode, and will override the global value of the noop setting. This means a resource with noop => false will be changed if necessary, even when running puppet agent with noop = true or --noop. (Conversely, a resource with noop => true will only be simulated, even when noop mode is globally disabled.)

  • Default: false


Perform one configuration run and exit, rather than spawning a long-running daemon. This is useful for interactively running puppet agent, or running puppet agent from cron.

  • Default: false


Where puppet agent stores the password for its private key. Generally unused.

  • Default: $privatedir/password


The shell search path. Defaults to whatever is inherited from the parent process.

This setting can only be set in the [main] section of puppet.conf; it cannot be set in [master], [agent], or an environment config section.

  • Default: none


The file containing the PID of a running process. This file is intended to be used by service management frameworks and monitoring systems to determine if a puppet process is still in the process table.

  • Default: $rundir/${run_mode}.pid


Where Puppet should store plugins that it pulls down from the central server.

  • Default: $libdir


Where Puppet should store external facts that are being handled by pluginsync

  • Default: $vardir/facts.d


Where to retrieve external facts for pluginsync

  • Default: puppet:///pluginfacts


What files to ignore when pulling down plugins.

  • Default: .svn CVS .git .hg


From where to retrieve plugins. The standard Puppet file type is used for retrieval, so anything that is a valid file source can be used here.

  • Default: puppet:///plugins


A command to run after every agent run. If this command returns a non-zero return code, the entire Puppet run will be considered to have failed, even though it might have performed work during the normal run.


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.

  • Default: json


A command to run before every agent run. If this command returns a non-zero return code, the entire Puppet run will fail.


The directory where catalog previews per node are generated.

  • Default: $vardir/preview


The scheduling priority of the process. Valid values are ‘high’, ‘normal’, ‘low’, or ‘idle’, which are mapped to platform-specific values. The priority can also be specified as an integer value and will be passed as is, e.g. -5. Puppet must be running as a privileged user in order to increase scheduling priority.

  • Default:


Where the client stores private certificate information.

  • Default: $ssldir/private


The private key directory.

  • Default: $ssldir/private_keys


Whether to enable experimental performance profiling

  • Default: false


The public key directory.

  • Default: $ssldir/public_keys


The fallback log file. This is only used when the --logdest option is not specified AND Puppet is running on an operating system where both the POSIX syslog service and the Windows Event Log are unavailable. (Currently, no supported operating systems match that description.)

Despite the name, both puppet agent and puppet master will use this file as the fallback logging destination.

For control over logging destinations, see the --logdest command line option in the manual pages for puppet master, puppet agent, and puppet apply. You can see man pages by running puppet <SUBCOMMAND> --help, or read them online at

  • Default: $logdir/puppetd.log


Whether to send reports after every transaction.

  • Default: true


The port to communicate with the report_server.

  • Default: $masterport


The server to send transaction reports to.

  • Default: $server


The directory in which to store reports. Each node gets a separate subdirectory in this directory. This setting is only used when the store report processor is enabled (see the reports setting).

  • Default: $vardir/reports


The list of report handlers to use. When using multiple report handlers, their names should be comma-separated, with whitespace allowed. (For example, reports = http, store.)

This setting is relevant to puppet master and puppet apply. The puppet master will call these report handlers with the reports it receives from agent nodes, and puppet apply will call them with its own report. (In all cases, the node applying the catalog must have report = true.)

See the report reference for information on the built-in report handlers; custom report handlers can also be loaded from modules. (Report handlers are loaded from the lib directory, at puppet/reports/NAME.rb.)

  • Default: store


The URL that reports should be forwarded to. This setting is only used when the http report processor is enabled (see the reports setting).

  • Default: http://localhost:3000/reports/upload


Where host certificate requests are stored.

  • Default: $ssldir/certificate_requests


The file in which puppet agent stores a list of the resources associated with the retrieved configuration.

  • Default: $statedir/resources.txt


The configuration file that defines the rights to the different rest indirections. This can be used as a fine-grained authorization system for puppet master. The puppet master command is deprecated and Puppet Server uses its own auth.conf that must be placed within its configuration directory.

  • Default: $confdir/auth.conf


Enables having extended data in the catalog by storing them as a hash with the special key __ptype. When enabled, resource containing values of the data types Binary, Regexp, SemVer, SemVerRange, Timespan and Timestamp, as well as instances of types derived from Object retain their data type.

  • Default: true


The YAML file containing indirector route configuration.

  • Default: $confdir/routes.yaml


Where Puppet PID files are kept.

  • Default: Unix/Linux: /var/run/puppetlabs – Windows: C:\ProgramData\PuppetLabs\puppet\var\run – Non-root user: ~/.puppetlabs/var/run


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 --no-client option. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: 30m


The maximum amount of time an agent run is allowed to take. A Puppet agent run that exceeds this timeout will be aborted. A value of 0 disables the timeout. Defaults to 1 hour. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: 1h


Where the serial number for certificates is stored.

  • Default: $cadir/serial


The puppet master server to which the puppet agent should connect.

  • Default: puppet


The directory in which serialized data is stored, usually in a subdirectory.

  • Default: $vardir/server_data


The list of puppet master servers to which the puppet agent should connect, in the order that they will be tried.

  • Default: []


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 diff/lcs Ruby library.

  • Default: false


Where the CA stores signed certificates.

  • Default: $cadir/signed


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.


The address the agent should use to initiate requests.

  • Default:


Whether to sleep for a random amount of time, ranging from immediately up to its $splaylimit, before performing its first agent run after a service restart. After this period, the agent runs periodically on its $runinterval.

For example, assume a default 30-minute $runinterval, splay set to its default of false, and an agent starting at :00 past the hour. The agent would check in every 30 minutes at :01 and :31 past the hour.

With splay enabled, it waits any amount of time up to its $splaylimit before its first run. For example, it might randomly wait 8 minutes, then start its first run at :08 past the hour. With the $runinterval at its default 30 minutes, its next run will be at :38 past the hour.

If you restart an agent’s puppet service with splay enabled, it recalculates its splay period and delays its first agent run after restarting for this new period. If you simultaneously restart a group of puppet agents with splay enabled, their checkins to your puppet masters can be distributed more evenly.

  • Default: false


The maximum time to delay before an agent’s first run when splay is enabled. Defaults to the agent’s $runinterval. The splay interval is random and recalculated each time the agent is started or restarted. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: $runinterval


The domain which will be queried to find the SRV records of servers to use.

  • Default: (the system’s own domain)


Certificate authorities who issue server certificates. SSL servers will not be considered authentic unless they possess a certificate issued by an authority listed in this file. If this setting has no value then the Puppet master’s CA certificate (localcacert) will be used.

  • Default:


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., / Puppet will parse out the Common Name (CN) from the Distinguished Name (DN) and use the value of the CN field for authorization.

Note that the name of the HTTP header gets munged by the web server common gateway interface: an HTTP_ prefix is added, dashes are converted to underscores, and all letters are uppercased. Thus, to use the X-Client-DN header, this setting should be HTTP_X_CLIENT_DN.

  • Default: HTTP_X_CLIENT_DN


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.

Note that the name of the HTTP header gets munged by the web server common gateway interface: an HTTP_ prefix is added, dashes are converted to underscores, and all letters are uppercased. Thus, to use the X-Client-Verify header, this setting should be HTTP_X_CLIENT_VERIFY.



A lock file to indicate that the ssl bootstrap process is currently in progress.

  • Default: $ssldir/ssl.lock


The setting is deprecated and has no effect. Ensure all root and intermediate certificate authorities used to issue client certificates are contained in the server’s cacert file on the server.

  • Default:


Where SSL certificates are kept.

  • Default: $confdir/ssl


The directory where Puppet state is stored. Generally, this directory can be removed without causing harm (although it might result in spurious service restarts).

  • Default: $vardir/state


Where puppet agent and puppet master store state associated with the running configuration. In the case of puppet master, this file reflects the state discovered through interacting with clients.

  • Default: $statedir/state.yaml


How long the Puppet agent should cache when a resource was last checked or synced. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y). A value of 0 or unlimited will disable cache pruning.

This setting affects the usage of schedule resources, as the information about when a resource was last checked (and therefore when it needs to be checked again) is stored in the statefile. The statettl needs to be large enough to ensure that a resource will not trigger multiple times during a schedule due to its entry expiring from the cache.

  • Default: 32d


Whether to compile a static catalog, which occurs only on a Puppet Server master when the code-id-command and code-content-command settings are configured in its puppetserver.conf file.

  • Default: true


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.

By default this uses the ‘puppetdb’ backend.

You can adjust the backend using the storeconfigs_backend setting.

  • Default: false


Configure the backend terminus used for StoreConfigs. By default, this uses the PuppetDB store, which must be installed and configured before turning on StoreConfigs.

  • Default: puppetdb


The strictness level of puppet. Allowed values are:

  • off - do not perform extra validation, do not report
  • warning - perform extra validation, report as warning (default)
  • error - perform extra validation, fail with error

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.

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.

  • Default: warning


Whether the agent specified environment should be considered authoritative, causing the run to fail if the retrieved catalog does not match it.

  • Default: false


Whether to only search for the complete hostname as it is in the certificate when searching for node information in the catalogs.

  • Default: false


Causes an evaluation error when referencing unknown variables. (This does not affect referencing variables that are explicitly set to undef).

  • Default: false


Whether to print a transaction summary.

  • Default: false


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, sha384, sha512, sha224, sha1, sha1lite, mtime, ctime. Default is md5, sha256, sha384, sha512, sha224.

  • Default: [“md5”, “sha256”, “sha384”, “sha512”, “sha224”]


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.

  • Default: daemon


Tags to use to find resources. If this is set, then only resources tagged with the specified tags will be applied. Values must be comma-separated.


Turns on experimental support for tasks and plans in the puppet language. This is for internal API use only. Do not change this setting.

  • Default: false


Whether to print stack traces on some errors

  • Default: false


Transactional storage file for persisting data between transactions for the purposes of infering information (such as corrective_change) on new data received.

  • Default: $statedir/transactionstore.yaml


File that provides mapping between custom SSL oids and user-friendly names

  • Default: $confdir/custom_trusted_oid_mapping.yaml


Whether to only use the cached catalog rather than compiling a new catalog on every run. Puppet can be run with this enabled by default and then selectively disabled when a recompile is desired. Because a Puppet agent using cached catalogs does not contact the master for a new catalog, it also does not upload facts at the beginning of the Puppet run.

  • Default: false


Whether the server will search for SRV records in DNS for the current domain.

  • Default: false


Whether to use the cached configuration when the remote configuration will not compile. This option is useful for testing new configurations, where you want to fix the broken configuration rather than reverting to a known-good one.

  • Default: true


The user Puppet Server will run as. Used to ensure the agent side processes (agent, apply, etc) create files and directories readable by Puppet Server when necessary.

  • Default: puppet


Where Puppet stores dynamic and growing data. The default for this setting is calculated specially, like confdir_.

  • Default: Unix/Linux: /opt/puppetlabs/puppet/cache – Windows: C:\ProgramData\PuppetLabs\puppet\cache – Non-root user: ~/.puppetlabs/opt/puppet/cache


The directory containing vendored modules. These modules will be used by all environments like those in the basemodulepath. The only difference is that modules in the basemodulepath are pluginsynced, while vendored modules are not

  • Default: /opt/puppetlabs/puppet/vendor_modules


How frequently puppet agent should ask for a signed certificate.

When starting for the first time, puppet agent will submit a certificate signing request (CSR) to the server named in the ca_server setting (usually the puppet master); this may be autosigned, or may need to be approved by a human, depending on the CA server’s configuration.

Puppet agent cannot apply configurations until its approved certificate is available. Since the certificate may or may not be available immediately, puppet agent will repeatedly try to fetch it at this interval. You can turn off waiting for certificates by specifying a time of 0, or a maximum amount of time to wait in the maxwaitforcert setting, in which case puppet agent will exit if it cannot get a cert. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).

  • Default: 2m


The directory in which YAML data is stored, usually in a subdirectory.

  • Default: $vardir/yaml
Back to top
The page rank or the 1 our of 5 rating a user has given the page.
The email address of the user submitting feedback.
The URL of the page being ranked/rated.