puppet 7.7.0 → 7.11.0

data/man/man5/puppet.conf.5

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPETCONF" "5" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPETCONF" "5" "September 2021" "Puppet, Inc." "Puppet manual"
 \fBThis page is autogenerated; any changes will get overwritten\fR
 .
 .SH "Configuration settings"
@@ -82,7 +82,7 @@ Whether log files should always flush to disk\.
 .IP "" 0
 .
 .SS "autosign"
-Whether (and how) to autosign certificate requests\. This setting is only relevant on a puppet master acting as a certificate authority (CA)\.
+Whether (and how) to autosign certificate requests\. This setting is only relevant on a Puppet Server acting as a certificate authority (CA)\.
 .
 .P
 Valid values are true (autosigns all certificate requests; not recommended), false (disables autosigning certificates), or the absolute path to a file\.
@@ -91,7 +91,7 @@ Valid values are true (autosigns all certificate requests; not recommended), fal
 The file specified in this setting may be either a \fBconfiguration file\fR or a \fBcustom policy executable\.\fR Puppet will automatically determine what it is: If the Puppet user (see the \fBuser\fR setting) can execute the file, it will be treated as a policy executable; otherwise, it will be treated as a config file\.
 .
 .P
-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 \fIas a command line argument,\fR and the contents of the CSR in PEM format \fIon stdin\.\fR 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 custom policy executable is configured, the CA Puppet Server will run it every time it receives a CSR\. The executable will be passed the subject CN of the request \fIas a command line argument,\fR and the contents of the CSR in PEM format \fIon stdin\.\fR It should exit with a status of 0 if the cert should be autosigned and non\-zero if the cert should not be autosigned\.
 .
 .P
 If a certificate request is not autosigned, it will persist for review\. An admin user can use the \fBpuppetserver ca sign\fR command to manually sign it, or can delete the request\.
@@ -264,7 +264,7 @@ When certificate_revocation is set to \'false\', Puppet disables all certificate
 .IP "" 0
 .
 .SS "certname"
-The name to use when handling certificates\. When a node requests a certificate from the CA puppet master, it uses the value of the \fBcertname\fR setting as its requested Subject CN\.
+The name to use when handling certificates\. When a node requests a certificate from the CA Puppet Server, it uses the value of the \fBcertname\fR setting as its requested Subject CN\.
 .
 .P
 This is the name used when managing a node\'s permissions in Puppet Server\'s auth\.conf \fIhttps://puppet\.com/docs/puppetserver/latest/config_file_auth\.html\fR\. In most cases, it is also used as the node\'s name when matching node definitions \fIhttps://puppet\.com/docs/puppet/latest/lang_node_definitions\.html\fR and requesting data from an ENC\. (This can be changed with the \fBnode_name_value\fR and \fBnode_name_fact\fR settings, although you should only do so if you have a compelling reason\.)
@@ -398,7 +398,7 @@ If the agent downloads a new CRL, the agent will use it for subsequent network r
 .IP "" 0
 .
 .SS "csr_attributes"
-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 \fBpuppetserver ca generate\fR command\.
+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 Server; if it does, unwanted certificate extensions may leak into certificates created with the \fBpuppetserver ca generate\fR command\.
 .
 .P
 If present, this file must be a YAML hash containing a \fBcustom_attributes\fR key and/or an \fBextension_requests\fR 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\.
@@ -579,10 +579,10 @@ Whether to document all resources when using \fBpuppet doc\fR to generate manife
 .IP "" 0
 .
 .SS "environment"
-The environment in which Puppet is running\. For clients, such as \fBpuppet agent\fR, this determines the environment itself, which Puppet uses to find modules and much more\. For servers, such as \fBpuppet master\fR, this provides the default environment for nodes that Puppet knows nothing about\.
+The environment in which Puppet is running\. For clients, such as \fBpuppet agent\fR, this determines the environment itself, which Puppet uses to find modules and much more\. For servers, such as \fBpuppet server\fR, this provides the default environment for nodes that Puppet knows nothing about\.
 .
 .P
-When defining an environment in the \fB[agent]\fR 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 \fBpuppet agent\fR\.
+When defining an environment in the \fB[agent]\fR section, this refers to the environment that the agent requests from the primary server\. The environment doesn\'t have to exist on the local filesystem because the agent fetches it from the primary server\. This definition is used when running \fBpuppet agent\fR\.
 .
 .P
 When defined in the \fB[user]\fR 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 \fBpuppet module\fR and \fBpuppet apply\fR, use this definition\.
@@ -689,6 +689,22 @@ For more info, see the ENC documentation \fIhttps://puppet\.com/docs/puppet/late
 .
 .IP "" 0
 .
+.SS "fact_name_length_soft_limit"
+The soft limit for the length of a fact name\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: \fB2560\fR
+.
+.IP "" 0
+.
+.SS "fact_value_length_soft_limit"
+The soft limit for the length of a fact value\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: \fB4096\fR
+.
+.IP "" 0
+.
 .SS "factpath"
 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 \';\'\.)
 .
@@ -851,7 +867,7 @@ Whether to write HTTP request and responses to stderr\. This should never be use
 .IP "" 0
 .
 .SS "http_extra_headers"
-The list of extra headers that will be sent with http requests to the master\. The header definition consists of a name and a value separated by a colon\.
+The list of extra headers that will be sent with http requests to the primary server\. The header definition consists of a name and a value separated by a colon\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fB[]\fR
@@ -913,7 +929,7 @@ The time to wait for data to be read from an HTTP connection\. If nothing is rea
 The HTTP User\-Agent string to send when making network requests\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: \fBPuppet/7\.7\.0 Ruby/2\.5\.1\-p57 (x86_64\-linux)\fR
+\fIDefault\fR: \fBPuppet/7\.11\.0 Ruby/2\.5\.1\-p57 (x86_64\-linux)\fR
 .
 .IP "" 0
 .
@@ -926,7 +942,7 @@ Whether the puppet run should ignore errors during pluginsync\. If the setting i
 .IP "" 0
 .
 .SS "ignoremissingtypes"
-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\.
+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 primary server is restarted\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fBfalse\fR
@@ -1143,7 +1159,7 @@ Whether Puppet should manage the owner, group, and mode of files it uses interna
 .IP "" 0
 .
 .SS "manifest"
-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 \.
+The entry\-point manifest for the primary server\. 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 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://puppet\.com/docs/puppet/latest/environments_about\.html\fR
@@ -1294,10 +1310,10 @@ How to store cached nodes\. Valid values are (none), \'json\', \'msgpack\', or \
 .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 Puppet Server\'s default auth\.conf \fIhttps://puppet\.com/docs/puppetserver/latest/config_file_auth\.html\fR\.
+The fact name used to determine the node name used for all requests the agent makes to the primary server\. WARNING: This setting is mutually exclusive with node_name_value\. Changing this setting also requires changes to Puppet Server\'s default auth\.conf \fIhttps://puppet\.com/docs/puppetserver/latest/config_file_auth\.html\fR\.
 .
 .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 Puppet Server\'s default auth\.conf \fIhttps://puppet\.com/docs/puppetserver/latest/config_file_auth\.html\fR\.
+The explicit value used for the node name for all requests the agent makes to the primary server\. WARNING: This setting is mutually exclusive with node_name_fact\. Changing this setting also requires changes to Puppet Server\'s default auth\.conf \fIhttps://puppet\.com/docs/puppetserver/latest/config_file_auth\.html\fR\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fB$certname\fR
@@ -1342,7 +1358,7 @@ The three main node data plugins are:
 Whether to apply catalogs in noop mode, which allows Puppet to partially simulate a normal run\. This setting affects puppet agent and puppet apply\.
 .
 .P
-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\.
+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 primary Puppet server, 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://puppet\.com/docs/puppet/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\.)
@@ -1352,6 +1368,14 @@ When running in noop mode, Puppet will check whether each resource is in sync, l
 .
 .IP "" 0
 .
+.SS "number_of_facts_soft_limit"
+The soft limit for the total number of facts\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: \fB2048\fR
+.
+.IP "" 0
+.
 .SS "onetime"
 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\.
 .
@@ -1379,6 +1403,14 @@ This setting can only be set in the \fB[main]\fR section of puppet\.conf; it can
 .
 .IP "" 0
 .
+.SS "payload_soft_limit"
+The soft limit for the size of the payload\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: \fB16777216\fR
+.
+.IP "" 0
+.
 .SS "pidfile"
 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\.
 .
@@ -1517,10 +1549,10 @@ Whether to print the Puppet stack trace on some errors\. This is a noop if \fBtr
 The fallback log file\. This is only used when the \fB\-\-logdest\fR 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\.)
 .
 .P
-Despite the name, both puppet agent and puppet master will use this file as the fallback logging destination\.
+Despite the name, both puppet agent and puppet server 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://puppet\.com/docs/puppet/latest/man/\.
+For control over logging destinations, see the \fB\-\-logdest\fR command line option in the manual pages for puppet server, puppet agent, and puppet apply\. You can see man pages by running \fBpuppet <SUBCOMMAND> \-\-help\fR, or read them online at https://puppet\.com/docs/puppet/latest/man/\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fB$logdir/puppetd\.log\fR
@@ -1571,11 +1603,14 @@ The directory in which to store reports\. Each node gets a separate subdirectory
 The list of report handlers to use\. When using multiple report handlers, their names should be comma\-separated, with whitespace allowed\. (For example, \fBreports = http, store\fR\.)
 .
 .P
-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 \fBreport = true\fR\.)
+This setting is relevant to puppet server and puppet apply\. The primary Puppet server 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 \fBreport = true\fR\.)
 .
 .P
 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 \fBpuppet/reports/NAME\.rb\fR\.)
 .
+.P
+To turn off reports entirely, set this to \fBnone\fR
+.
 .IP "\(bu" 4
 \fIDefault\fR: \fBstore\fR
 .
@@ -1662,7 +1697,7 @@ Where the serial number for certificates is stored\.
 .IP "" 0
 .
 .SS "server"
-The puppet master server to which the puppet agent should connect\.
+The primary Puppet server to which the Puppet agent should connect\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fBpuppet\fR
@@ -1678,7 +1713,7 @@ 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\. Each value should be a fully qualified domain name, followed by an optional \':\' and port number\. If a port is omitted, Puppet uses masterport for that host\.
+The list of primary Puppet servers to which the Puppet agent should connect, in the order that they will be tried\. Each value should be a fully qualified domain name, followed by an optional \':\' and port number\. If a port is omitted, Puppet uses masterport for that host\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fB[]\fR
@@ -1738,7 +1773,7 @@ For example, assume a default 30\-minute \fB$runinterval\fR, \fBsplay\fR set to
 With \fBsplay\fR enabled, it waits any amount of time up to its \fB$splaylimit\fR before its first run\. For example, it might randomly wait 8 minutes, then start its first run at :08 past the hour\. With the \fB$runinterval\fR at its default 30 minutes, its next run will be at :38 past the hour\.
 .
 .P
-If you restart an agent\'s puppet service with \fBsplay\fR 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 \fBsplay\fR enabled, their checkins to your puppet masters can be distributed more evenly\.
+If you restart an agent\'s puppet service with \fBsplay\fR 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 \fBsplay\fR enabled, their checkins to your primary servers can be distributed more evenly\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fBfalse\fR
@@ -1816,7 +1851,7 @@ The directory where Puppet state is stored\. Generally, this directory can be re
 .IP "" 0
 .
 .SS "statefile"
-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\.
+Where Puppet agent and Puppet Server store state associated with the running configuration\. In the case of Puppet Server, this file reflects the state discovered through interacting with clients\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fB$statedir/state\.yaml\fR
@@ -1835,7 +1870,7 @@ This setting affects the usage of \fBschedule\fR resources, as the information a
 .IP "" 0
 .
 .SS "static_catalogs"
-Whether to compile a static catalog \fIhttps://puppet\.com/docs/puppet/latest/static_catalogs\.html#enabling\-or\-disabling\-static\-catalogs\fR, which occurs only on a Puppet Server master when the \fBcode\-id\-command\fR and \fBcode\-content\-command\fR settings are configured in its \fBpuppetserver\.conf\fR file\.
+Whether to compile a static catalog \fIhttps://puppet\.com/docs/puppet/latest/static_catalogs\.html#enabling\-or\-disabling\-static\-catalogs\fR, which occurs only on Puppet Server when the \fBcode\-id\-command\fR and \fBcode\-content\-command\fR settings are configured in its \fBpuppetserver\.conf\fR file\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fBtrue\fR
@@ -1879,7 +1914,7 @@ 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\.
+The strictness level is for both language semantics and runtime evaluation validation\. In addition to controlling the behavior with this primary server 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\.
@@ -1940,6 +1975,14 @@ Turns on experimental support for tasks and plans in the puppet language\. This
 .
 .IP "" 0
 .
+.SS "top_level_facts_soft_limit"
+The soft limit for the number of top level facts\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: \fB512\fR
+.
+.IP "" 0
+.
 .SS "trace"
 Whether to print stack traces on some errors\. Will print internal Ruby stack trace interleaved with Puppet function frames\.
 .
@@ -1987,7 +2030,7 @@ File that provides mapping between custom SSL oids and user\-friendly names
 .IP "" 0
 .
 .SS "use_cached_catalog"
-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\.
+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 primary server for a new catalog, it also does not upload facts at the beginning of the Puppet run\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: \fBfalse\fR
@@ -2046,7 +2089,7 @@ Whether or not to look for versioned environment directories, symlinked from \fB
 How frequently puppet agent should ask for a signed certificate\.
 .
 .P
-When starting for the first time, puppet agent will submit a certificate signing request (CSR) to the server named in the \fBca_server\fR 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\.
+When starting for the first time, puppet agent will submit a certificate signing request (CSR) to the server named in the \fBca_server\fR setting (usually the primary Puppet server); this may be autosigned, or may need to be approved by a human, depending on the CA server\'s configuration\.
 .
 .P
 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 \fBmaxwaitforcert\fR 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)\.
@@ -2067,6 +2110,14 @@ This argument is by default disabled (value set to 0)\. In this case puppet agen
 .
 .IP "" 0
 .
+.SS "write_catalog_summary"
+Whether to write the \fBclassfile\fR and \fBresourcefile\fR after applying the catalog\. It is enabled by default, except when running \fBpuppet apply\fR\.
+.
+.IP "\(bu" 4
+\fIDefault\fR: \fBtrue\fR
+.
+.IP "" 0
+.
 .SS "yamldir"
 The directory in which YAML data is stored, usually in a subdirectory\.
 .

data/man/man8/puppet-agent.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-AGENT" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-AGENT" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-agent\fR \- The puppet agent daemon
@@ -164,6 +164,9 @@ A path ending with \'\.jsonl\' will receive structured output in JSON Lines form
 .IP "\(bu" 4
 \-\-waitforcert: This option only matters for daemons that do not yet have certificates and it is enabled by default, with a value of 120 (seconds)\. This causes \'puppet agent\' to connect to the server every 2 minutes and ask it to sign a certificate request\. This is useful for the initial setup of a puppet client\. You can turn off waiting for certificates by specifying a time of 0\. (This is a Puppet setting, and can go in puppet\.conf\.)
 .
+.IP "\(bu" 4
+\-\-write_catalog_summary After compiling the catalog saves the resource list and classes list to the node in the state directory named classes\.txt and resources\.txt (This is a Puppet setting, and can go in puppet\.conf\.)
+.
 .IP "" 0
 .
 .SH "EXAMPLE"

data/man/man8/puppet-apply.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-APPLY" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-APPLY" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-apply\fR \- Apply Puppet manifests locally

data/man/man8/puppet-catalog.8

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CATALOG" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CATALOG" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-catalog\fR \- Compile, save, view, and convert catalogs\.
 .
 .SH "SYNOPSIS"
-puppet catalog \fIaction\fR [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet catalog \fIaction\fR [\-\-terminus _TERMINUS]
 .
 .SH "DESCRIPTION"
 This subcommand deals with catalogs, which are compiled per\-node artifacts generated from a set of Puppet manifests\. By default, it interacts with the compiling subsystem and compiles a catalog using the default manifest and \fBcertname\fR, but you can change the source of the catalog with the \fB\-\-terminus\fR option\. You can also choose to print any catalog in \'dot\' format (for easy graph viewing with OmniGraffle or Graphviz) with \'\-\-render\-as dot\'\.
@@ -51,7 +51,7 @@ The terminus for an action is often determined by context, but occasionally need
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog apply [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet catalog apply [\-\-terminus _TERMINUS]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -70,7 +70,7 @@ Nothing\. When used from the Ruby API, returns a Puppet::Transaction::Report obj
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog compile [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet catalog compile [\-\-terminus _TERMINUS]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -89,7 +89,7 @@ A serialized catalog\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog download [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet catalog download [\-\-terminus _TERMINUS]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -117,7 +117,7 @@ When used from the Ruby API, this action has a side effect of leaving Puppet::Re
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog find [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIcertname\fR
+puppet catalog find [\-\-terminus _TERMINUS] \fIcertname\fR
 .
 .IP
 \fBDESCRIPTION\fR
@@ -136,7 +136,7 @@ A serialized catalog\. When used from the Ruby API, returns a Puppet::Resource::
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog info [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet catalog info [\-\-terminus _TERMINUS]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -149,7 +149,7 @@ Prints the default terminus class for this subcommand\. Note that different run
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog save [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIkey\fR
+puppet catalog save [\-\-terminus _TERMINUS] \fIkey\fR
 .
 .IP
 \fBDESCRIPTION\fR
@@ -162,7 +162,7 @@ API only: create or overwrite an object\. As the Faces framework does not curren
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog select [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIhost\fR \fIresource_type\fR
+puppet catalog select [\-\-terminus _TERMINUS] \fIhost\fR \fIresource_type\fR
 .
 .IP
 \fBDESCRIPTION\fR

data/man/man8/puppet-config.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CONFIG" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CONFIG" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-config\fR \- Interact with Puppet\'s settings\.

data/man/man8/puppet-describe.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-DESCRIBE" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DESCRIBE" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-describe\fR \- Display help about resource types

data/man/man8/puppet-device.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-DEVICE" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DEVICE" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-device\fR \- Manage remote network devices

data/man/man8/puppet-doc.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-DOC" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DOC" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-doc\fR \- Generate Puppet references

data/man/man8/puppet-epp.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-EPP" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-EPP" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-epp\fR \- Interact directly with the EPP template parser/renderer\.

data/man/man8/puppet-facts.8

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-FACTS" "8" "May 2021" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-FACTS" "8" "September 2021" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-facts\fR \- Retrieve and store facts\.
 .
 .SH "SYNOPSIS"
-puppet facts \fIaction\fR [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet facts \fIaction\fR [\-\-terminus _TERMINUS]
 .
 .SH "DESCRIPTION"
 This subcommand manages facts, which are collections of normalized system information used by Puppet\. It can read facts directly from the local system (with the default \fBfacter\fR terminus)\.
@@ -51,7 +51,7 @@ The terminus for an action is often determined by context, but occasionally need
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts find [\-\-terminus _TERMINUS] [\-\-extra HASH] [\fInode_certname\fR]
+puppet facts find [\-\-terminus _TERMINUS] [\fInode_certname\fR]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -79,7 +79,7 @@ When using the \fBfacter\fR terminus, the host argument is ignored\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts info [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet facts info [\-\-terminus _TERMINUS]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -92,7 +92,7 @@ Prints the default terminus class for this subcommand\. Note that different run
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts save [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIkey\fR
+puppet facts save [\-\-terminus _TERMINUS] \fIkey\fR
 .
 .IP
 \fBDESCRIPTION\fR
@@ -105,7 +105,7 @@ API only: create or overwrite an object\. As the Faces framework does not curren
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts [\-\-terminus _TERMINUS] [\-\-extra HASH] [\-\-config\-file \fIpath\fR] [\-\-custom\-dir \fIpath\fR] [\-\-external\-dir \fIpath\fR] [\-\-no\-block] [\-\-no\-cache] [\-\-show\-legacy] [\-\-value\-only] [\-\-timing] [\fIfacts\fR]
+puppet facts [\-\-terminus _TERMINUS] [\-\-config\-file \fIpath\fR] [\-\-custom\-dir \fIpath\fR] [\-\-external\-dir \fIpath\fR] [\-\-no\-block] [\-\-no\-cache] [\-\-show\-legacy] [\-\-value\-only] [\-\-timing] [\fIfacts\fR]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -151,7 +151,7 @@ The output of facter with added puppet specific facts\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts upload [\-\-terminus _TERMINUS] [\-\-extra HASH]
+puppet facts upload [\-\-terminus _TERMINUS]
 .
 .IP
 \fBDESCRIPTION\fR