puppet 6.29.0 → 7.0.0

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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-AGENT" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-agent\fR \- The puppet agent daemon
@@ -126,7 +126,7 @@ Disable can also take an optional message that will be reported by the \'puppet
 \-\-job\-id: Attach the specified job id to the catalog request and the report used for this agent run\. This option only works when \'\-\-onetime\' is used\. When using Puppet Enterprise this flag should not be used as the orchestrator sets the job\-id for you and it must be unique\.
 .
 .IP "\(bu" 4
-\-\-logdest: 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\. If debugging or verbosity is enabled, this defaults to \'console\'\. Otherwise, it defaults to \'syslog\' on POSIX systems and \'eventlog\' on Windows\. Multiple destinations can be set using a comma separated list (eg: \fB/path/file1,console,/path/file2\fR)"
+\-\-logdest: 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\. If debugging or verbosity is enabled, this defaults to \'console\'\. Otherwise, it defaults to \'syslog\' on POSIX systems and \'eventlog\' on Windows\.
 .
 .IP
 A path ending with \'\.json\' will receive structured output in JSON format\. The log file will not have an ending \']\' automatically written to it due to the appending nature of logging\. It must be appended manually to make the content valid JSON\.
@@ -164,9 +164,6 @@ 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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-APPLY" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-apply\fR \- Apply Puppet manifests locally
@@ -55,7 +55,7 @@ See the configuration file documentation at https://puppet\.com/docs/puppet/late
 \-\-loadclasses: Load any stored classes\. \'puppet agent\' caches configured classes (usually at /etc/puppetlabs/puppet/classes\.txt), and setting this option causes all of those classes to be set in your puppet manifest\.
 .
 .IP "\(bu" 4
-\-\-logdest: 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\. Defaults to \'console\'\. Multiple destinations can be set using a comma separated list (eg: \fB/path/file1,console,/path/file2\fR)"
+\-\-logdest: 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\. Defaults to \'console\'\.
 .
 .IP
 A path ending with \'\.json\' will receive structured output in JSON format\. The log file will not have an ending \']\' automatically written to it due to the appending nature of logging\. It must be appended manually to make the content valid JSON\.

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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CATALOG" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-catalog\fR \- Compile, save, view, and convert catalogs\.
 .
 .SH "SYNOPSIS"
-puppet catalog \fIaction\fR [\-\-terminus _TERMINUS]
+puppet catalog \fIaction\fR [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .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]
+puppet catalog apply [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .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]
+puppet catalog compile [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -89,7 +89,7 @@ A serialized catalog\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet catalog download [\-\-terminus _TERMINUS]
+puppet catalog download [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .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] \fIcertname\fR
+puppet catalog find [\-\-terminus _TERMINUS] [\-\-extra HASH] \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]
+puppet catalog info [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .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] \fIkey\fR
+puppet catalog save [\-\-terminus _TERMINUS] [\-\-extra HASH] \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] \fIhost\fR \fIresource_type\fR
+puppet catalog select [\-\-terminus _TERMINUS] [\-\-extra HASH] \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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CONFIG" "8" "November 2020" "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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DESCRIBE" "8" "November 2020" "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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DEVICE" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-device\fR \- Manage remote network devices
@@ -56,7 +56,7 @@ Enable full debugging\.
 .
 .TP
 \-\-logdest, \-l
-Where to send log messages\. Choose between \'syslog\' (the POSIX syslog service), \'console\', or the path to a log file\. If debugging or verbosity is enabled, this defaults to \'console\'\. Otherwise, it defaults to \'syslog\'\. Multiple destinations can be set using a comma separated list (eg: \fB/path/file1,console,/path/file2\fR)"
+Where to send log messages\. Choose between \'syslog\' (the POSIX syslog service), \'console\', or the path to a log file\. If debugging or verbosity is enabled, this defaults to \'console\'\. Otherwise, it defaults to \'syslog\'\.
 .
 .IP
 A path ending with \'\.json\' will receive structured output in JSON format\. The log file will not have an ending \']\' automatically written to it due to the appending nature of logging\. It must be appended manually to make the content valid JSON\.

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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DOC" "8" "November 2020" "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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-EPP" "8" "November 2020" "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" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-FACTS" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-facts\fR \- Retrieve and store facts\.
 .
 .SH "SYNOPSIS"
-puppet facts \fIaction\fR [\-\-terminus _TERMINUS]
+puppet facts \fIaction\fR [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .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)\.
@@ -47,39 +47,11 @@ The terminus for an action is often determined by context, but occasionally need
 .SH "ACTIONS"
 .
 .TP
-\fBdiff\fR \- Compare Facter 3 output with Facter 4 output
-\fBSYNOPSIS\fR
-.
-.IP
-puppet facts diff [\-\-terminus _TERMINUS] [\-\-structured] [\-\-exclude \fIregex\fR]
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-Compares output from facter 3 with Facter 4 and prints the differences
-.
-.IP
-\fBOPTIONS\fR \fI\-\-exclude <regex\fR> \- Regex used to exclude specific facts from diff\.
-.
-.IP
-\fI\-\-structured\fR \- Render the different facts as structured\.
-.
-.IP
-\fBRETURNS\fR
-.
-.IP
-Differences between Facter 3 and Facter 4 output as an array\.
-.
-.IP
-\fBNOTES\fR
-.
-.TP
 \fBfind\fR \- Retrieve a node\'s facts\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts [\-\-terminus _TERMINUS] [\fInode_certname\fR]
+puppet facts find [\-\-terminus _TERMINUS] [\-\-extra HASH] [\fInode_certname\fR]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -107,7 +79,7 @@ When using the \fBfacter\fR terminus, the host argument is ignored\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts info [\-\-terminus _TERMINUS]
+puppet facts info [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -120,7 +92,7 @@ Prints the default terminus class for this subcommand\. Note that different run
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts save [\-\-terminus _TERMINUS] \fIkey\fR
+puppet facts save [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIkey\fR
 .
 .IP
 \fBDESCRIPTION\fR
@@ -133,7 +105,7 @@ API only: create or overwrite an object\. As the Faces framework does not curren
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts show [\-\-terminus _TERMINUS] [\-\-config\-file \fIpath\fR] [\-\-custom\-dir \fIpath\fR] [\-\-external\-dir \fIpath\fR] [\-\-no\-block] [\-\-no\-cache] [\-\-show\-legacy] [\-\-value\-only] [\fIfacts\fR]
+puppet facts [\-\-terminus _TERMINUS] [\-\-extra HASH] [\-\-config\-file \fIpath\fR] [\-\-custom\-dir \fIpath\fR] [\-\-external\-dir \fIpath\fR] [\-\-no\-block] [\-\-no\-cache] [\-\-show\-legacy] [\fIfacts\fR]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -160,9 +132,6 @@ Reads facts from the local system using \fBfacter\fR terminus\. A query can be p
 \fI\-\-show\-legacy\fR \- Show legacy facts when querying all facts\.
 .
 .IP
-\fI\-\-value\-only\fR \- Show only the value when the action is called with a single query
-.
-.IP
 \fBRETURNS\fR
 .
 .IP
@@ -176,7 +145,7 @@ The output of facter with added puppet specific facts\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet facts upload [\-\-terminus _TERMINUS]
+puppet facts upload [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -194,7 +163,7 @@ Nothing\.
 \fBNOTES\fR
 .
 .IP
-This action requires that the puppet master\'s \fBauth\.conf\fR file allow \fBPUT\fR or \fBsave\fR access to the \fB/puppet/v3/facts\fR API endpoint\.
+This action requires that the Puppet Server\'s \fBauth\.conf\fR file allow \fBPUT\fR or \fBsave\fR access to the \fB/puppet/v3/facts\fR API endpoint\.
 .
 .IP
 For details on configuring Puppet Server\'s \fBauth\.conf\fR, see:
@@ -202,19 +171,7 @@ For details on configuring Puppet Server\'s \fBauth\.conf\fR, see:
 .IP
 \fIhttps://puppet\.com/docs/puppetserver/latest/config_file_auth\.html\fR
 .
-.IP
-For legacy Rack\-based Puppet Masters, see:
-.
-.IP
-\fIhttps://puppet\.com/docs/puppet/latest/config_file_auth\.html\fR
-.
 .SH "EXAMPLES"
-\fBdiff\fR
-.
-.P
-get differences between facter versions: $ puppet facts diff
-.
-.P
 \fBfind\fR
 .
 .P

data/man/man8/puppet-filebucket.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-FILEBUCKET" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-FILEBUCKET" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-filebucket\fR \- Store and retrieve files in a filebucket
@@ -16,13 +16,13 @@ puppet filebucket \fImode\fR [\-h|\-\-help] [\-V|\-\-version] [\-d|\-\-debug] [\
 Puppet filebucket can operate in three modes, with only one mode per call:
 .
 .P
-backup: Send one or more files to the specified file bucket\. Each sent file is printed with its resulting md5 sum\.
+backup: Send one or more files to the specified file bucket\. Each sent file is printed with its resulting sha256 sum\.
 .
 .P
-get: Return the text associated with an md5 sum\. The text is printed to stdout, and only one file can be retrieved at a time\.
+get: Return the text associated with an sha256 sum\. The text is printed to stdout, and only one file can be retrieved at a time\.
 .
 .P
-restore: Given a file path and an md5 sum, store the content associated with the sum into the specified file path\. You can specify an entirely new path to this argument; you are not restricted to restoring the content to its original location\.
+restore: Given a file path and an sha256 sum, store the content associated with the sum into the specified file path\. You can specify an entirely new path to this argument; you are not restricted to restoring the content to its original location\.
 .
 .P
 diff: Print a diff in unified format between two checksums in the filebucket or between a checksum and its matching file\.

data/man/man8/puppet-generate.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-GENERATE" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-GENERATE" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-generate\fR \- Generates Puppet code from Ruby definitions\.

data/man/man8/puppet-help.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-HELP" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-HELP" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-help\fR \- Display Puppet help\.

data/man/man8/puppet-lookup.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-LOOKUP" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-LOOKUP" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-lookup\fR \- Interactive Hiera lookup
@@ -22,7 +22,10 @@ The most common version of this command is:
 puppet lookup [\-\-help] [\-\-type \fITYPESTRING\fR] [\-\-merge first|unique|hash|deep] [\-\-knock\-out\-prefix \fIPREFIX\-STRING\fR] [\-\-sort\-merged\-arrays] [\-\-merge\-hash\-arrays] [\-\-explain] [\-\-environment \fIENV\fR] [\-\-default \fIVALUE\fR] [\-\-node \fINODE\-NAME\fR] [\-\-facts \fIFILE\fR] [\-\-compile] [\-\-render\-as s|json|yaml|binary|msgpack] \fIkeys\fR
 .
 .SH "DESCRIPTION"
-The lookup command is a CLI for Puppet\'s \'lookup()\' function\. It searches your Hiera data and returns a value for the requested lookup key, so you can test and explore your data\. It is a modern replacement for the \'hiera\' command\. Lookup uses the setting for global hiera\.yaml from puppet\'s config, and the environment to find the environment level hiera\.yaml as well as the resulting modulepath for the environment (for hiera\.yaml files in modules)\. Hiera usually relies on a node\'s facts to locate the relevant data sources\. By default, \'puppet lookup\' uses facts from the node you run the command on, but you can get data for any other node with the \'\-\-node \fINAME\fR\' option\. If possible, the lookup command will use the requested node\'s real stored facts from PuppetDB; if PuppetDB isn\'t configured or you want to provide arbitrary fact values, you can pass alternate facts as a JSON or YAML file with \'\-\-facts \fIFILE\fR\'\.
+The lookup command is a CLI for Puppet\'s \'lookup()\' function\. It searches your Hiera data and returns a value for the requested lookup key, so you can test and explore your data\. It is a modern replacement for the \'hiera\' command\.
+.
+.P
+Hiera usually relies on a node\'s facts to locate the relevant data sources\. By default, \'puppet lookup\' uses facts from the node you run the command on, but you can get data for any other node with the \'\-\-node \fINAME\fR\' option\. If possible, the lookup command will use the requested node\'s real stored facts from PuppetDB; if PuppetDB isn\'t configured or you want to provide arbitrary fact values, you can pass alternate facts as a JSON or YAML file with \'\-\-facts \fIFILE\fR\'\.
 .
 .P
 If you\'re debugging your Hiera data and want to see where values are coming from, use the \'\-\-explain\' option\.
@@ -51,7 +54,7 @@ For more details about how Hiera works, see the Hiera documentation: https://pup
 \-\-facts \fIFILE\fR Specify a \.json or \.yaml file of key => value mappings to override the facts for this lookup\. Any facts not specified in this file maintain their original value\.
 .
 .IP "\(bu" 4
-\-\-environment \fIENV\fR Like with most Puppet commands, you can specify an environment on the command line\. This is important for lookup because different environments can have different Hiera data\. This environment will be always be the one used regardless of any other factors\.
+\-\-environment \fIENV\fR Like with most Puppet commands, you can specify an environment on the command line\. This is important for lookup because different environments can have different Hiera data\.
 .
 .IP "\(bu" 4
 \-\-merge first|unique|hash|deep: Specify the merge behavior, overriding any merge behavior from the data\'s lookup_options\. \'first\' returns the first value found\. \'unique\' appends everything to a merged, deduplicated array\. \'hash\' performs a simple hash merge by overwriting keys of lower lookup priority\. \'deep\' performs a deep merge on values of Array and Hash type\. There are additional options that can be used with \'deep\'\.
@@ -86,12 +89,6 @@ For more details about how Hiera works, see the Hiera documentation: https://pup
 To look up \'key_name\' using the Puppet Server node\'s facts: $ puppet lookup key_name
 .
 .P
-To look up \'key_name\' using the Puppet Server node\'s arbitrary variables from a manifest, and classify the node if applicable: $ puppet lookup key_name \-\-compile
-.
-.P
-To look up \'key_name\' using the Puppet Server node\'s facts, overridden by facts given in a file: $ puppet lookup key_name \-\-facts fact_file\.yaml
-.
-.P
 To look up \'key_name\' with agent\.local\'s facts: $ puppet lookup \-\-node agent\.local key_name
 .
 .P

data/man/man8/puppet-module.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-MODULE" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-MODULE" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-module\fR \- Creates, installs and searches for modules on the Puppet Forge\.
@@ -32,10 +32,10 @@ Whether to log debug information\.
 .
 .TP
 \-\-environment production
-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\.
+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\.
 .
 .IP
-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\.
+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\.
 .
 .IP
 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\.
@@ -53,19 +53,6 @@ Setting a global value for \fBmodulepath\fR in puppet\.conf is not allowed (but
 .SH "ACTIONS"
 .
 .TP
-\fBbuild\fR \- Build a module release package\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet module build
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-This action has been replaced by Puppet Development Kit\. For more information visit https://puppet\.com/docs/pdk/latest/pdk\.html\.
-.
-.TP
 \fBchanges\fR \- Show modified files of an installed module\.
 \fBSYNOPSIS\fR
 .
@@ -85,19 +72,6 @@ Shows any files in a module that have been modified since it was installed\. Thi
 Array of strings representing paths of modified files\.
 .
 .TP
-\fBgenerate\fR \- Generate boilerplate for a new module\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet module generate
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-This action has been replaced by Puppet Development Kit\. For more information visit https://puppet\.com/docs/pdk/latest/pdk\.html\.
-.
-.TP
 \fBinstall\fR \- Install a module from the Puppet Forge or a release archive\.
 \fBSYNOPSIS\fR
 .
@@ -160,28 +134,6 @@ The output of this action includes information from the module\'s metadata, incl
 hash of paths to module objects
 .
 .TP
-\fBsearch\fR \- Search the Puppet Forge for a module\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet module search \fIsearch_term\fR
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-This action has been deprecated\. Please use the Puppet Forge to search for modules\.
-.
-.IP
-Searches a repository for modules whose names, descriptions, or keywords match the provided search term\.
-.
-.IP
-\fBRETURNS\fR
-.
-.IP
-Array of module metadata hashes
-.
-.TP
 \fBuninstall\fR \- Uninstall a puppet module\.
 \fBSYNOPSIS\fR
 .
@@ -322,15 +274,6 @@ List installed modules from a specified modulepath:
 $ puppet module list \-\-modulepath /opt/puppetlabs/puppet/modules /opt/puppetlabs/puppet/modules (no modules installed)
 .
 .P
-\fBsearch\fR
-.
-.P
-Search the Puppet Forge for a module:
-.
-.P
-$ puppet module search puppetlabs NAME DESCRIPTION AUTHOR KEYWORDS bacula This is a generic Apache module @puppetlabs backups
-.
-.P
 \fBuninstall\fR
 .
 .P

data/man/man8/puppet-node.8

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-NODE" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-NODE" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-node\fR \- View and manage node definitions\.
 .
 .SH "SYNOPSIS"
-puppet node \fIaction\fR [\-\-terminus _TERMINUS]
+puppet node \fIaction\fR [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .SH "DESCRIPTION"
 This subcommand interacts with node objects, which are used by Puppet to build a catalog\. A node object consists of the node\'s facts, environment, node parameters (exposed in the parser as top\-scope variables), and classes\.
@@ -51,7 +51,7 @@ The terminus for an action is often determined by context, but occasionally need
 \fBSYNOPSIS\fR
 .
 .IP
-puppet node clean [\-\-terminus _TERMINUS] \fIhost1\fR [\fIhost2\fR \.\.\.]
+puppet node clean [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIhost1\fR [\fIhost2\fR \.\.\.]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -79,7 +79,7 @@ NOTE: this action now cleans up certs via Puppet Server\'s CA API\. A running se
 \fBSYNOPSIS\fR
 .
 .IP
-puppet node find [\-\-terminus _TERMINUS] \fIhost\fR
+puppet node find [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIhost\fR
 .
 .IP
 \fBDESCRIPTION\fR
@@ -101,7 +101,7 @@ RENDERING ISSUES: Rendering as string and json are currently broken; node object
 \fBSYNOPSIS\fR
 .
 .IP
-puppet node info [\-\-terminus _TERMINUS]
+puppet node info [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .IP
 \fBDESCRIPTION\fR

data/man/man8/puppet-parser.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-PARSER" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-PARSER" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-parser\fR \- Interact directly with the parser\.

data/man/man8/puppet-plugin.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-PLUGIN" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-PLUGIN" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-plugin\fR \- Interact with the Puppet plugin system\.

data/man/man8/puppet-report.8

@@ -1,13 +1,13 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-REPORT" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-REPORT" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-report\fR \- Create, display, and submit reports\.
 .
 .SH "SYNOPSIS"
-puppet report \fIaction\fR [\-\-terminus _TERMINUS]
+puppet report \fIaction\fR [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .SH "OPTIONS"
 Note that any setting that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid settings, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
@@ -48,7 +48,7 @@ The terminus for an action is often determined by context, but occasionally need
 \fBSYNOPSIS\fR
 .
 .IP
-puppet report info [\-\-terminus _TERMINUS]
+puppet report info [\-\-terminus _TERMINUS] [\-\-extra HASH]
 .
 .IP
 \fBDESCRIPTION\fR
@@ -61,7 +61,7 @@ Prints the default terminus class for this subcommand\. Note that different run
 \fBSYNOPSIS\fR
 .
 .IP
-puppet report save [\-\-terminus _TERMINUS] \fIreport\fR
+puppet report save [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIreport\fR
 .
 .IP
 \fBDESCRIPTION\fR
@@ -80,7 +80,7 @@ Nothing\.
 \fBSYNOPSIS\fR
 .
 .IP
-puppet report submit [\-\-terminus _TERMINUS] \fIreport\fR
+puppet report submit [\-\-terminus _TERMINUS] [\-\-extra HASH] \fIreport\fR
 .
 .IP
 \fBDESCRIPTION\fR

data/man/man8/puppet-resource.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-RESOURCE" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-RESOURCE" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-resource\fR \- The resource abstraction layer shell

data/man/man8/puppet-script.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-SCRIPT" "8" "January 2023" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-SCRIPT" "8" "November 2020" "Puppet, Inc." "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-script\fR \- Run a puppet manifests as a script without compiling a catalog
@@ -34,7 +34,7 @@ Print this help message
 .
 .TP
 \-\-logdest
-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\. Defaults to \'console\'\. Multiple destinations can be set using a comma separated list (eg: \fB/path/file1,console,/path/file2\fR)"
+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\. Defaults to \'console\'\.
 .
 .IP
 A path ending with \'\.json\' will receive structured output in JSON format\. The log file will not have an ending \']\' automatically written to it due to the appending nature of logging\. It must be appended manually to make the content valid JSON\.