puppet 5.3.7-x86-mingw32 → 5.4.0-x86-mingw32

data/man/man5/puppet.conf.5

@@ -1,10 +1,10 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPETCONF" "5" "May 2018" "Puppet, Inc." "Puppet manual"
-\fBThis page is autogenerated; any changes will get overwritten\fR
+.TH "PUPPETCONF" "5" "June 2017" "Puppet Labs, LLC" "Puppet manual"
+\fBThis page is autogenerated; any changes will get overwritten\fR \fI(last generated on 2017\-06\-29 14:42:23 \-0700)\fR
 .
-.SH "Configuration settings"
+.SH "Configuration Settings"
 .
 .IP "\(bu" 4
 Each of these settings can be specified in \fBpuppet\.conf\fR or on the command line\.
@@ -22,9 +22,6 @@ Multiple values should be specified as comma\-separated lists; multiple director
 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)\.
 .
 .IP "\(bu" 4
-If you use the \fBsplay\fR setting, note that the period that it waits changes each time the Puppet agent is restarted\.
-.
-.IP "\(bu" 4
 Settings that take a single file or directory can optionally set the owner, group, and mode for their value: \fBrundir = $vardir/run { owner = puppet, group = puppet, mode = 644 }\fR
 .
 .IP "\(bu" 4
@@ -33,7 +30,7 @@ The Puppet executables will ignore any setting that isn\'t relevant to their fun
 .IP "" 0
 .
 .P
-See the configuration guide \fIhttps://puppet\.com/docs/puppet/latest/config_about_settings\.html\fR for more details\.
+See the configuration guide \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/config_about_settings\.html\fR for more details\.
 .
 .SS "agent_catalog_run_lockfile"
 A lock file to indicate that a puppet agent catalog run is currently in progress\. The file contains the pid of the process that holds the lock on the catalog run\.
@@ -271,22 +268,10 @@ The certificate directory\.
 .IP "" 0
 .
 .SS "certificate_revocation"
-Whether certificate revocation checking should be enabled, and what level of checking should be performed\.
-.
-.P
-When certificate_revocation is set to \'true\' or \'chain\', Puppet will download the CA CRL and will perform revocation checking against each certificate in the chain\.
-.
-.P
-Puppet is unable to load multiple CRLs, so if certificate_revocation is set to \'chain\' and Puppet attempts to verify a certificate signed by a root CA the behavior is equivalent to the \'leaf\' setting, and if Puppet attempts to verify a certificate signed by an intermediate CA then verification will fail as Puppet will be unable to load the multiple CRLs required for full chain checking\. As such the \'chain\' setting is limited in functionality and is meant as a stand in pending the implementation of full chain checking\.
-.
-.P
-When certificate_revocation is set to \'leaf\', Puppet will download the CA CRL and will verify the leaf certificate against that CRL\. CRLs will not be fetched or checked for the rest of the certificates in the chain\. If you are using an intermediate CA certificate and want to enable certificate revocation checking, this setting must be set to \'leaf\'\.
-.
-.P
-When certificate_revocation is set to \'false\', Puppet will disable all certificate revocation checking and will not attempt to download the CRL\.
+Whether certificate revocation should be supported by downloading a Certificate Revocation List (CRL) to all clients\. If enabled, CA chaining will almost definitely not work\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: chain
+\fIDefault\fR: true
 .
 .IP "" 0
 .
@@ -311,7 +296,7 @@ The special value \fBca\fR is reserved, and can\'t be used as the certname for a
 Defaults to the node\'s fully qualified domain name\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: the Host\'s fully qualified domain name, as determined by facter
+\fIDefault\fR: rll\.corp\.puppetlabs\.net
 .
 .IP "" 0
 .
@@ -518,14 +503,6 @@ Which digest algorithm to use for file resources and the filebucket\. Valid valu
 .
 .IP "" 0
 .
-.SS "disable_i18n"
-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\.
-.
-.IP "\(bu" 4
-\fIDefault\fR: false
-.
-.IP "" 0
-.
 .SS "disable_per_environment_manifest"
 Whether to disallow an environment\-specific main manifest\. When set to \fBtrue\fR, Puppet will use the manifest specified in the \fBdefault_manifest\fR setting for all environments\. If an environment specifies a different main manifest in its \fBenvironment\.conf\fR file, catalog requests for that environment will fail with an error\.
 .
@@ -604,16 +581,7 @@ 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\.
-.
-.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\.
-.
-.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\.
-.
-.P
-Given that the context and effects vary depending on the config section \fIhttps://puppet\.com/docs/puppet/latest/config_file_main\.html#config\-sections\fR in which the \fBenvironment\fR setting is defined, do not set it globally\.
+The environment Puppet is running in\. For clients (e\.g\., \fBpuppet agent\fR) this determines the environment itself, which is used to find modules and much more\. For servers (i\.e\., \fBpuppet master\fR) this provides the default environment for nodes we know nothing about\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: production
@@ -760,14 +728,6 @@ Freezes the \'main\' class, disallowing any code to be added to it\. This essent
 .
 .IP "" 0
 .
-.SS "future_features"
-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\.
-.
-.IP "\(bu" 4
-\fIDefault\fR: false
-.
-.IP "" 0
-.
 .SS "genconfig"
 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 \fBgenconfig\fR itself)\. This setting only makes sense when specified on the command line as \fB\-\-genconfig\fR\.
 .
@@ -935,7 +895,7 @@ The time to wait for one block to be read from an HTTP connection\. If nothing i
 The HTTP User\-Agent string to send when making network requests\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: Puppet/5\.3\.7 Ruby/2\.3\.1\-p112 (x86_64\-linux)
+\fIDefault\fR: Puppet/5\.0\.0 Ruby/2\.4\.1\-p111 (x86_64\-darwin15)
 .
 .IP "" 0
 .
@@ -1084,22 +1044,6 @@ Where each client stores the CA certificate\.
 .
 .IP "" 0
 .
-.SS "localedest"
-Where Puppet should store translation files that it pulls down from the central server\.
-.
-.IP "\(bu" 4
-\fIDefault\fR: $vardir/locales
-.
-.IP "" 0
-.
-.SS "localesource"
-From where to retrieve translation files\. The standard Puppet \fBfile\fR type is used for retrieval, so anything that is a valid file source can be used here\.
-.
-.IP "\(bu" 4
-\fIDefault\fR: puppet:///locales
-.
-.IP "" 0
-.
 .SS "log_level"
 Default logging level for messages from Puppet\. Allowed values are:
 .
@@ -1622,14 +1566,6 @@ How often puppet agent applies the catalog\. Note that a runinterval of 0 means
 .
 .IP "" 0
 .
-.SS "runtimeout"
-The maximum amount of time an agent run is allowed to take\. A Puppet agent run that exceeds this timeout will be aborted\. Defaults to 0, which is unlimited\. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y)\.
-.
-.IP "\(bu" 4
-\fIDefault\fR: 0
-.
-.IP "" 0
-.
 .SS "serial"
 Where the serial number for certificates is stored\.
 .
@@ -1680,25 +1616,12 @@ Where the CA stores signed certificates\.
 .
 .SS "skip_tags"
 Tags to use to filter resources\. If this is set, then only resources not tagged with the specified tags will be applied\. Values must be comma\-separated\.
-.
-.SS "sourceaddress"
-The address the agent should use to initiate requests\.
-.
-.TP
-\fIDefault\fR:
-
 .
 .SS "splay"
-Whether to sleep for a random amount of time, ranging from immediately up to its \fB$splaylimit\fR, before performing its first agent run after a service restart\. After this period, the agent runs periodically on its \fB$runinterval\fR\.
+Whether to sleep for a pseudo\-random (but consistent) amount of time before a run\.
 .
 .P
-For example, assume a default 30\-minute \fB$runinterval\fR, \fBsplay\fR set to its default of \fBfalse\fR, and an agent starting at :00 past the hour\. The agent would check in every 30 minutes at :01 and :31 past the hour\.
-.
-.P
-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\.
+For example, without \fBsplay\fR enabled, your agent checks in every 30 minutes at :01 and :31 past the hour\. After enabling \fBsplay\fR, the agent will wait the pseudorandom sleep time, say eight minutes, and then check in every 30 minutes, at :09 and :39 after the hour\. If you restart the same agent at 12:45 PM, it will wait its eight minutes, and check in at 12:52 PM, and every 30 minutes after that, at 1:22 PM, 1:52 PM, and so on\. Other agents will have different sleep times, and so will check in at different times even if they are all restarted at the same time\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: false
@@ -1706,7 +1629,7 @@ If you restart an agent\'s puppet service with \fBsplay\fR enabled, it recalcula
 .IP "" 0
 .
 .SS "splaylimit"
-The maximum time to delay before an agent\'s first run when \fBsplay\fR is enabled\. Defaults to the agent\'s \fB$runinterval\fR\. The \fBsplay\fR 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)\.
+The maximum time to delay before runs\. Defaults to being the same as the run interval\. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y)\.
 .
 .IP "\(bu" 4
 \fIDefault\fR: $runinterval
@@ -1717,7 +1640,7 @@ The maximum time to delay before an agent\'s first run when \fBsplay\fR is enabl
 The domain which will be queried to find the SRV records of servers to use\.
 .
 .IP "\(bu" 4
-\fIDefault\fR: delivery\.puppetlabs\.net
+\fIDefault\fR: corp\.puppetlabs\.net
 .
 .IP "" 0
 .
@@ -1980,4 +1903,6 @@ The directory in which YAML data is stored, usually in a subdirectory\.
 \fIDefault\fR: $vardir/yaml
 .
 .IP "" 0
-
+.
+.P
+\fIThis page autogenerated on 2017\-06\-29 14:42:23 \-0700\fR

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 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-AGENT" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-agent\fR \- The puppet agent daemon
@@ -13,7 +13,7 @@ Retrieves the client configuration from the puppet master and applies it to the
 This service may be run as a daemon, run periodically using cron (or something similar), or run interactively for testing purposes\.
 .
 .SH "USAGE"
-puppet agent [\-\-certname \fINAME\fR] [\-D|\-\-daemonize|\-\-no\-daemonize] [\-d|\-\-debug] [\-\-detailed\-exitcodes] [\-\-digest \fIDIGEST\fR] [\-\-disable [MESSAGE]] [\-\-enable] [\-\-fingerprint] [\-h|\-\-help] [\-l|\-\-logdest syslog|eventlog|\fIABS FILEPATH\fR|console] [\-\-masterport \fIPORT\fR] [\-\-noop] [\-o|\-\-onetime] [\-\-sourceaddress \fIIP_ADDRESS\fR] [\-t|\-\-test] [\-v|\-\-verbose] [\-V|\-\-version] [\-w|\-\-waitforcert \fISECONDS\fR]
+puppet agent [\-\-certname \fINAME\fR] [\-D|\-\-daemonize|\-\-no\-daemonize] [\-d|\-\-debug] [\-\-detailed\-exitcodes] [\-\-digest \fIDIGEST\fR] [\-\-disable [MESSAGE]] [\-\-enable] [\-\-fingerprint] [\-h|\-\-help] [\-l|\-\-logdest syslog|eventlog|\fIFILE\fR|console] [\-\-masterport \fIPORT\fR] [\-\-noop] [\-o|\-\-onetime] [\-t|\-\-test] [\-v|\-\-verbose] [\-V|\-\-version] [\-w|\-\-waitforcert \fISECONDS\fR]
 .
 .SH "DESCRIPTION"
 This is the main puppet client\. Its job is to retrieve the local machine\'s configuration from a remote server and apply it\. In order to successfully communicate with the remote server, the client must have a certificate signed by a certificate authority that the server trusts; the recommended method for this, at the moment, is to run a certificate authority as part of the puppet server (which is the default)\. The client will connect and request a signed certificate, and will continue connecting until it receives one\.
@@ -133,10 +133,6 @@ Use \'noop\' mode where the daemon runs in a no\-op or dry\-run mode\. This is u
 Run the configuration once\. Runs a single (normally daemonized) Puppet run\. Useful for interactively running puppet agent when used in conjunction with the \-\-no\-daemonize option\. (This is a Puppet setting, and can go in puppet\.conf\. Note the special \'no\-\' prefix for boolean settings on the command line\.)
 .
 .TP
-\-\-sourceaddress
-Set the source IP address for transactions\. This defaults to automatically selected\. (This is a Puppet setting, and can go in puppet\.conf\.)
-.
-.TP
 \-\-test
 Enable the most common options used for testing\. These are \'onetime\', \'verbose\', \'no\-daemonize\', \'no\-usecacheonfailure\', \'detailed\-exitcodes\', \'no\-splay\', and \'show_diff\'\.
 .

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 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-APPLY" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-apply\fR \- Apply Puppet manifests locally
@@ -10,7 +10,7 @@
 Applies a standalone Puppet manifest to the local system\.
 .
 .SH "USAGE"
-puppet apply [\-h|\-\-help] [\-V|\-\-version] [\-d|\-\-debug] [\-v|\-\-verbose] [\-e|\-\-execute] [\-\-detailed\-exitcodes] [\-L|\-\-loadclasses] [\-l|\-\-logdest syslog|eventlog|\fIABS FILEPATH\fR|console] [\-\-noop] [\-\-catalog \fIcatalog\fR] [\-\-write\-catalog\-summary] \fIfile\fR
+puppet apply [\-h|\-\-help] [\-V|\-\-version] [\-d|\-\-debug] [\-v|\-\-verbose] [\-e|\-\-execute] [\-\-detailed\-exitcodes] [\-L|\-\-loadclasses] [\-l|\-\-logdest syslog|eventlog|\fIFILE\fR|console] [\-\-noop] [\-\-catalog \fIcatalog\fR] [\-\-write\-catalog\-summary] \fIfile\fR
 .
 .SH "DESCRIPTION"
 This is the standalone puppet execution tool; use it to apply individual manifests\.

data/man/man8/puppet-ca.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CA" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CA" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-ca\fR \- Local Puppet Certificate Authority management\.

data/man/man8/puppet-catalog.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CATALOG" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CATALOG" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-catalog\fR \- Compile, save, view, and convert catalogs\.

data/man/man8/puppet-cert.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CERT" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CERT" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-cert\fR \- Manage certificates and requests

data/man/man8/puppet-certificate.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CERTIFICATE" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CERTIFICATE" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-certificate\fR \- Provide access to the CA for certificate management\.

data/man/man8/puppet-certificate_request.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CERTIFICATE_REQUEST" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CERTIFICATE_REQUEST" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-certificate_request\fR \- Manage certificate requests\.

data/man/man8/puppet-certificate_revocation_list.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-CERTIFICATE_REVOCATION_LIST" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CERTIFICATE_REVOCATION_LIST" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-certificate_revocation_list\fR \- Manage the list of revoked certificates\.

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 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-CONFIG" "8" "June 2017" "Puppet Labs, LLC" "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 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DESCRIBE" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-describe\fR \- Display help about resource types

data/man/man8/puppet-device.8

@@ -1,43 +1,37 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-DEVICE" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DEVICE" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-device\fR \- Manage remote network devices
 .
 .SH "SYNOPSIS"
-Retrieves catalogs from the Puppet master and applies them to remote devices\.
+Retrieves all configurations from the puppet master and apply them to the remote devices configured in /etc/puppetlabs/puppet/device\.conf\.
 .
 .P
-This subcommand can be run manually; or periodically using cron, a scheduled task, or a similar tool\.
+Currently must be run out periodically, using cron or something similar\.
 .
 .SH "USAGE"
-puppet device [\-d|\-\-debug] [\-\-detailed\-exitcodes] [\-\-deviceconfig \fIfile\fR] [\-h|\-\-help] [\-l|\-\-logdest syslog|\fIfile\fR|console] [\-v|\-\-verbose] [\-w|\-\-waitforcert \fIseconds\fR] [\-a|\-\-apply \fIfile\fR] [\-r|\-\-resource \fItype\fR [name]] [\-t|\-\-target \fIdevice\fR] [\-\-user=\fIuser\fR] [\-V|\-\-version]
+puppet device [\-d|\-\-debug] [\-\-detailed\-exitcodes] [\-\-deviceconfig \fIfile\fR] [\-h|\-\-help] [\-l|\-\-logdest syslog|\fIfile\fR|console] [\-v|\-\-verbose] [\-w|\-\-waitforcert \fIseconds\fR] [\-t|\-\-target \fIdevice\fR] [\-V|\-\-version]
 .
 .SH "DESCRIPTION"
-Devices require a proxy Puppet agent to request certificates, collect facts, retrieve and apply catalogs, and store reports\.
+Once the client has a signed certificate for a given remote device, it will retrieve its configuration and apply it\.
 .
 .SH "USAGE NOTES"
-Devices managed by the puppet\-device subcommand on a Puppet agent are configured in device\.conf, which is located at $confdir/device\.conf by default, and is configurable with the $deviceconfig setting\.
+One need a /etc/puppetlabs/puppet/device\.conf file with the following content:
 .
 .P
-The device\.conf file is an INI\-like file, with one section per device:
+[remote\.device\.fqdn] type \fItype\fR url \fIurl\fR
 .
 .P
-[\fIDEVICE_CERTNAME\fR] type \fITYPE\fR url \fIURL\fR debug
+where: * type: the current device type (the only value at this time is cisco) * url: an url allowing to connect to the device
 .
 .P
-The section name specifies the certname of the device\.
+Supported url must conforms to: scheme://user:password@hostname/?query
 .
 .P
-The values for the type and url properties are specific to each type of device\.
-.
-.P
-The optional debug property specifies transport\-level debugging, and is limited to telnet and ssh transports\.
-.
-.P
-See https://docs\.puppet\.com/puppet/latest/config_file_device\.html for details\.
+with: * scheme: either ssh or telnet * user: username, can be omitted depending on the switch/router configuration * password: the connection password * query: this is device specific\. Cisco devices supports an enable parameter whose value would be the enable password\.
 .
 .SH "OPTIONS"
 Note that any setting that\'s valid in the configuration file is also a valid long argument\. For example, \'server\' is a valid configuration parameter, so you can specify \'\-\-server \fIservername\fR\' as an argument\.
@@ -66,26 +60,10 @@ Where to send log messages\. Choose between \'syslog\' (the POSIX syslog service
 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\.
 .
 .TP
-\-\-apply
-Apply a manifest against a remote target\. Target must be specified\.
-.
-.TP
-\-\-resource
-Displays a resource state as Puppet code, roughly equivalent to \fBpuppet resource\fR\. Can be filterd by title\. Requires \-\-target be specified\.
-.
-.TP
 \-\-target
 Target a specific device/certificate in the device\.conf\. Doing so will perform a device run against only that device/certificate\.
 .
 .TP
-\-\-to_yaml
-Output found resources in yaml format, suitable to use with Hiera and create_resources\.
-.
-.TP
-\-\-user
-The user to run as\.
-.
-.TP
 \-\-verbose
 Turn on verbose reporting\.
 .
@@ -97,7 +75,7 @@ This option only matters for daemons that do not yet have certificates and it is
 .
 .nf
 
-  $ puppet device \-\-target remotehost \-\-verbose
+  $ puppet device \-\-server puppet\.domain\.com
 .
 .fi
 .

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 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-DOC" "8" "June 2017" "Puppet Labs, LLC" "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 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-EPP" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-epp\fR \- Interact directly with the EPP template parser/renderer\.

data/man/man8/puppet-facts.8

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PUPPET\-FACTS" "8" "May 2018" "Puppet, Inc." "Puppet manual"
+.TH "PUPPET\-FACTS" "8" "June 2017" "Puppet Labs, LLC" "Puppet manual"
 .
 .SH "NAME"
 \fBpuppet\-facts\fR \- Retrieve and store facts\.