puppet 4.4.0-universal-darwin

data/man/man8/puppet-certificate_revocation_list.8

@@ -0,0 +1,139 @@
+.\" generated with Ronn/v0.7.3
+.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "PUPPET\-CERTIFICATE_REVOCATION_LIST" "8" "May 2015" "Puppet Labs, LLC" "Puppet manual"
+.
+.SH "NAME"
+\fBpuppet\-certificate_revocation_list\fR \- Manage the list of revoked certificates\.
+.
+.SH "SYNOPSIS"
+puppet certificate_revocation_list \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra HASH]
+.
+.SH "DESCRIPTION"
+This subcommand is primarily for retrieving the certificate revocation list from the CA\.
+.
+.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\.
+.
+.P
+See the configuration file documentation at \fIhttps://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
+.
+.TP
+\-\-render\-as FORMAT
+The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
+.
+.TP
+\-\-verbose
+Whether to log verbosely\.
+.
+.TP
+\-\-debug
+Whether to log debug information\.
+.
+.TP
+\-\-extra HASH
+A terminus can take additional arguments to refine the operation, which are passed as an arbitrary hash to the back\-end\. Anything passed as the extra value is just send direct to the back\-end\.
+.
+.TP
+\-\-terminus TERMINUS
+Indirector faces expose indirected subsystems of Puppet\. These subsystems are each able to retrieve and alter a specific type of data (with the familiar actions of \fBfind\fR, \fBsearch\fR, \fBsave\fR, and \fBdestroy\fR) from an arbitrary number of pluggable backends\. In Puppet parlance, these backends are called terminuses\.
+.
+.IP
+Almost all indirected subsystems have a \fBrest\fR terminus that interacts with the puppet master\'s data\. Most of them have additional terminuses for various local data models, which are in turn used by the indirected subsystem on the puppet master whenever it receives a remote request\.
+.
+.IP
+The terminus for an action is often determined by context, but occasionally needs to be set explicitly\. See the "Notes" section of this face\'s manpage for more details\.
+.
+.SH "ACTIONS"
+.
+.TP
+\fBdestroy\fR \- Delete the certificate revocation list\.
+\fBSYNOPSIS\fR
+.
+.IP
+puppet certificate_revocation_list destroy [\-\-terminus TERMINUS] [\-\-extra HASH] \fIdummy_text\fR
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+Deletes the certificate revocation list\. This cannot be done over REST, but it is possible to delete the locally cached copy or the local CA\'s copy of the CRL\.
+.
+.IP
+\fBRETURNS\fR
+.
+.IP
+Nothing\.
+.
+.IP
+\fBNOTES\fR
+.
+.IP
+Although this action always deletes the CRL from the specified terminus, it requires a dummy argument; this is a known bug\.
+.
+.TP
+\fBfind\fR \- Retrieve the certificate revocation list\.
+\fBSYNOPSIS\fR
+.
+.IP
+puppet certificate_revocation_list find [\-\-terminus TERMINUS] [\-\-extra HASH] [\fIkey\fR]
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+Retrieve the certificate revocation list\.
+.
+.IP
+\fBRETURNS\fR
+.
+.IP
+The certificate revocation list\. When used from the Ruby API: returns an OpenSSL::X509::CRL object\.
+.
+.IP
+\fBNOTES\fR
+.
+.IP
+Although this action always returns the CRL from the specified terminus\.
+.
+.TP
+\fBinfo\fR \- Print the default terminus class for this face\.
+\fBSYNOPSIS\fR
+.
+.IP
+puppet certificate_revocation_list info [\-\-terminus TERMINUS] [\-\-extra HASH]
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
+.
+.SH "EXAMPLES"
+\fBfind\fR
+.
+.P
+Retrieve a copy of the puppet master\'s CRL:
+.
+.P
+$ puppet certificate_revocation_list find \-\-terminus rest
+.
+.SH "NOTES"
+This subcommand is an indirector face, which exposes \fBfind\fR, \fBsearch\fR, \fBsave\fR, and \fBdestroy\fR actions for an indirected subsystem of Puppet\. Valid termini for this face include:
+.
+.IP "\(bu" 4
+\fBca\fR
+.
+.IP "\(bu" 4
+\fBdisabled_ca\fR
+.
+.IP "\(bu" 4
+\fBfile\fR
+.
+.IP "\(bu" 4
+\fBrest\fR
+.
+.IP "" 0
+.
+.SH "COPYRIGHT AND LICENSE"
+Copyright 2011 by Puppet Labs Apache 2 license; see COPYING

data/man/man8/puppet-config.8

@@ -0,0 +1,117 @@
+.\" generated with Ronn/v0.7.3
+.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "PUPPET\-CONFIG" "8" "May 2015" "Puppet Labs, LLC" "Puppet manual"
+.
+.SH "NAME"
+\fBpuppet\-config\fR \- Interact with Puppet\'s settings\.
+.
+.SH "SYNOPSIS"
+puppet config \fIaction\fR [\-\-section SECTION_NAME]
+.
+.SH "DESCRIPTION"
+This subcommand can inspect and modify settings from Puppet\'s \'puppet\.conf\' configuration file\. For documentation about individual settings, see https://docs\.puppetlabs\.com/references/latest/configuration\.html\.
+.
+.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\.
+.
+.P
+See the configuration file documentation at \fIhttps://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
+.
+.TP
+\-\-render\-as FORMAT
+The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
+.
+.TP
+\-\-verbose
+Whether to log verbosely\.
+.
+.TP
+\-\-debug
+Whether to log debug information\.
+.
+.TP
+\-\-section SECTION_NAME
+The section of the puppet\.conf configuration file to interact with\.
+.
+.IP
+The three most commonly used sections are \'main\', \'master\', and \'agent\'\. \'Main\' is the default, and is used by all Puppet applications\. Other sections can override \'main\' values for specific applications \-\-\- the \'master\' section affects puppet master and puppet cert, and the \'agent\' section affects puppet agent\.
+.
+.IP
+Less commonly used is the \'user\' section, which affects puppet apply\. Any other section will be treated as the name of a legacy environment (a deprecated feature), and can only include the \'manifest\' and \'modulepath\' settings\.
+.
+.SH "ACTIONS"
+.
+.TP
+\fBprint\fR \- Examine Puppet\'s current settings\.
+\fBSYNOPSIS\fR
+.
+.IP
+puppet config print [\-\-section SECTION_NAME] (all | \fIsetting\fR [\fIsetting\fR \.\.\.]
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+Prints the value of a single setting or a list of settings\.
+.
+.IP
+This action is an alternate interface to the information available with \fBpuppet <subcommand> \-\-configprint\fR\.
+.
+.IP
+\fBNOTES\fR
+.
+.IP
+By default, this action reads the general configuration in the \'main\' section\. Use the \'\-\-section\' and \'\-\-environment\' flags to examine other configuration domains\.
+.
+.TP
+\fBset\fR \- Set Puppet\'s settings\.
+\fBSYNOPSIS\fR
+.
+.IP
+puppet config set [\-\-section SECTION_NAME] [setting_name] [setting_value]
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+Updates values in the \fBpuppet\.conf\fR configuration file\.
+.
+.IP
+\fBNOTES\fR
+.
+.IP
+By default, this action manipulates the configuration in the \'main\' section\. Use the \'\-\-section\' flag to manipulate other configuration domains\.
+.
+.SH "EXAMPLES"
+\fBprint\fR
+.
+.P
+Get puppet\'s runfile directory:
+.
+.P
+$ puppet config print rundir
+.
+.P
+Get a list of important directories from the master\'s config:
+.
+.P
+$ puppet config print all \-\-section master | grep \-E "(path|dir)"
+.
+.P
+\fBset\fR
+.
+.P
+Set puppet\'s runfile directory:
+.
+.P
+$ puppet config set rundir /var/run/puppetlabs
+.
+.P
+Set the vardir for only the agent:
+.
+.P
+$ puppet config set vardir /opt/puppetlabs/puppet/cache \-\-section agent
+.
+.SH "COPYRIGHT AND LICENSE"
+Copyright 2011 by Puppet Labs Apache 2 license; see COPYING

data/man/man8/puppet-describe.8

@@ -0,0 +1,51 @@
+.\" generated with Ronn/v0.7.3
+.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "PUPPET\-DESCRIBE" "8" "May 2015" "Puppet Labs, LLC" "Puppet manual"
+.
+.SH "NAME"
+\fBpuppet\-describe\fR \- Display help about resource types
+.
+.SH "SYNOPSIS"
+Prints help about Puppet resource types, providers, and metaparameters\.
+.
+.SH "USAGE"
+puppet describe [\-h|\-\-help] [\-s|\-\-short] [\-p|\-\-providers] [\-l|\-\-list] [\-m|\-\-meta]
+.
+.SH "OPTIONS"
+.
+.TP
+\-\-help
+Print this help text
+.
+.TP
+\-\-providers
+Describe providers in detail for each type
+.
+.TP
+\-\-list
+List all types
+.
+.TP
+\-\-meta
+List all metaparameters
+.
+.TP
+\-\-short
+List only parameters without detail
+.
+.SH "EXAMPLE"
+.
+.nf
+
+$ puppet describe \-\-list
+$ puppet describe file \-\-providers
+$ puppet describe user \-s \-m
+.
+.fi
+.
+.SH "AUTHOR"
+David Lutterkort
+.
+.SH "COPYRIGHT"
+Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2\.0 License

data/man/man8/puppet-device.8

@@ -0,0 +1,78 @@
+.\" generated with Ronn/v0.7.3
+.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "PUPPET\-DEVICE" "8" "May 2015" "Puppet Labs, LLC" "Puppet manual"
+.
+.SH "NAME"
+\fBpuppet\-device\fR \- Manage remote network devices
+.
+.SH "SYNOPSIS"
+Retrieves all configurations from the puppet master and apply them to the remote devices configured in /etc/puppetlabs/puppet/device\.conf\.
+.
+.P
+Currently must be run out periodically, using cron or something similar\.
+.
+.SH "USAGE"
+puppet device [\-d|\-\-debug] [\-\-detailed\-exitcodes] [\-V|\-\-version] [\-h|\-\-help] [\-l|\-\-logdest syslog|\fIfile\fR|console] [\-v|\-\-verbose] [\-w|\-\-waitforcert \fIseconds\fR]
+.
+.SH "DESCRIPTION"
+Once the client has a signed certificate for a given remote device, it will retrieve its configuration and apply it\.
+.
+.SH "USAGE NOTES"
+One need a /etc/puppetlabs/puppet/device\.conf file with the following content:
+.
+.P
+[remote\.device\.fqdn] type \fItype\fR url \fIurl\fR
+.
+.P
+where: * type: the current device type (the only value at this time is cisco) * url: an url allowing to connect to the device
+.
+.P
+Supported url must conforms to: scheme://user:password@hostname/?query
+.
+.P
+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\.
+.
+.TP
+\-\-debug
+Enable full debugging\.
+.
+.TP
+\-\-detailed\-exitcodes
+Provide transaction information via exit codes\. If this is enabled, an exit code of \'1\' means at least one device had a compile failure, an exit code of \'2\' means at least one device had resource changes, and an exit code of \'4\' means at least one device had resource failures\. Exit codes of \'3\', \'5\', \'6\', or \'7\' means that a bitwise combination of the preceeding exit codes happened\.
+.
+.TP
+\-\-help
+Print this help message
+.
+.TP
+\-\-logdest
+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\.
+.
+.TP
+\-\-verbose
+Turn on verbose reporting\.
+.
+.TP
+\-\-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\.
+.
+.SH "EXAMPLE"
+.
+.nf
+
+  $ puppet device \-\-server puppet\.domain\.com
+.
+.fi
+.
+.SH "AUTHOR"
+Brice Figureau
+.
+.SH "COPYRIGHT"
+Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2\.0 License

data/man/man8/puppet-doc.8

@@ -0,0 +1,46 @@
+.\" generated with Ronn/v0.7.3
+.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "PUPPET\-DOC" "8" "May 2015" "Puppet Labs, LLC" "Puppet manual"
+.
+.SH "NAME"
+\fBpuppet\-doc\fR \- Generate Puppet references
+.
+.SH "SYNOPSIS"
+Generates a reference for all Puppet types\. Largely meant for internal Puppet Labs use\. (Deprecated)
+.
+.SH "USAGE"
+puppet doc [\-h|\-\-help] [\-l|\-\-list] [\-r|\-\-reference \fIreference\-name\fR]
+.
+.SH "DESCRIPTION"
+This deprecated command generates a Markdown document to stdout describing all installed Puppet types or all allowable arguments to puppet executables\. It is largely meant for internal use and is used to generate the reference document available on the Puppet Labs web site\.
+.
+.P
+For Puppet module documentation (and all other use cases) this command has been superseded by the "puppet\-strings" module \- see https://github\.com/puppetlabs/puppetlabs\-strings for more information\.
+.
+.P
+This command (puppet\-doc) will be removed once the puppetlabs internal documentation processing pipeline is completely based on puppet\-strings\.
+.
+.SH "OPTIONS"
+.
+.TP
+\-\-help
+Print this help message
+.
+.TP
+\-\-reference
+Build a particular reference\. Get a list of references by running \'puppet doc \-\-list\'\.
+.
+.SH "EXAMPLE"
+.
+.nf
+
+$ puppet doc \-r type > /tmp/type_reference\.markdown
+.
+.fi
+.
+.SH "AUTHOR"
+Luke Kanies
+.
+.SH "COPYRIGHT"
+Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2\.0 License

data/man/man8/puppet-epp.8

@@ -0,0 +1,349 @@
+.\" generated with Ronn/v0.7.3
+.\" https://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "PUPPET\-EPP" "8" "May 2015" "Puppet Labs, LLC" "Puppet manual"
+.
+.SH "NAME"
+\fBpuppet\-epp\fR \- Interact directly with the EPP template parser/renderer\.
+.
+.SH "SYNOPSIS"
+puppet epp \fIaction\fR
+.
+.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\.
+.
+.P
+See the configuration file documentation at \fIhttps://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
+.
+.TP
+\-\-render\-as FORMAT
+The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
+.
+.TP
+\-\-verbose
+Whether to log verbosely\.
+.
+.TP
+\-\-debug
+Whether to log debug information\.
+.
+.SH "ACTIONS"
+.
+.TP
+\fBdump\fR \- Outputs a dump of the internal template parse tree for debugging
+\fBSYNOPSIS\fR
+.
+.IP
+puppet epp dump [\-\-e \fIsource\fR] [\-\-[no\-]validate] [\-\-[no\-]header] \-e \fIsource\fR | [\fItemplates\fR \.\.\.]
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+The dump action parses and validates the EPP syntax and dumps the resulting AST model in a human readable (but not necessarily an easy to understand) format\. The output format of the dumped tree is intended for epp parser debugging purposes and is not API, and may thus change between versions without deprecation warnings\.
+.
+.IP
+The command accepts one or more templates (\.epp) files, or an \-e followed by the template source text\. The given templates can be paths to template files, or references to templates in modules when given on the form \fImodulename\fR/\fItemplate\-name\fR\.epp\. If no arguments are given, the stdin is read (unless it is attached to a terminal)
+.
+.IP
+If multiple templates are given, they are separated with a header indicating the name of the template\. This can be surpressed with the option \-\-no\-header\. The option \-\-[no\-]header has no effect whe a single template is dumped\.
+.
+.IP
+When debugging the epp parser itself, it may be useful to surpress the valiation step with the \fB\-\-no\-validate\fR option to observe what the parser produced from the given source\.
+.
+.IP
+This command ignores the \-\-render\-as setting/option\.
+.
+.IP
+\fBOPTIONS\fR \fI\-\-e <source\fR> \- Dump one epp source expression given on the command line\.
+.
+.IP
+\fI\-\-[no\-]header\fR \- Whether or not to show a file name header between files\.
+.
+.IP
+\fI\-\-[no\-]validate\fR \- Whether or not to validate the parsed result, if no\-validate only syntax errors are reported\.
+.
+.IP
+\fBRETURNS\fR
+.
+.IP
+A dump of the resulting AST model unless there are syntax or validation errors\.
+.
+.TP
+\fBrender\fR \- Renders an epp template as text
+\fBSYNOPSIS\fR
+.
+.IP
+puppet epp render [\-\-e \fIsource\fR] [\-\-values \fIvalues_hash\fR] [\-\-values_file \fIpp_or_yaml_file\fR] [\-\-facts \fIyaml_file\fR] [\-\-[no\-]header] \-e \fIsource\fR | [\fItemplates\fR \.\.\.]
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+This action renders one or more EPP templates\.
+.
+.IP
+The command accepts one or more templates (\.epp files), given the same way as templates are given to the puppet \fBepp\fR function (a full path, or a relative reference on the form \'\fImodulename\fR/\fItemplate\-name\fR\.epp\'), or as a relative path\.args In case the given path matches both a modulename/template and a file, the template from the module is used\.
+.
+.IP
+An inline_epp equivalent can also be performed by giving the template after an \-e, or by piping the EPP source text to the command\.
+.
+.IP
+Values to the template can be defined using the Puppet Language on the command line with \fB\-\-values\fR or in a \.pp or \.yaml file referenced with \fB\-\-values_file\fR\. If specifying both the result is merged with \-\-values having higher precedence\.
+.
+.IP
+The \-\-values option allows a Puppet Language sequence of expressions to be defined on the command line the same way as it may be given in a \.pp file referenced with \fB\-\-values_file\fR\. It may set variable values (that become available in the template), and must produce either \fBundef\fR or a \fBHash\fR of values (the hash may be empty)\. Producing \fBundef\fR simulates that the template is called without an arguments hash and thus only references variables in its outer scope\. When a hash is given, a template is limited to seeing only the global scope\. It is thus possible to simulate the different types of calls to the \fBepp\fR and \fBinline_epp\fR functions, with or without a given hash\. Note that if variables are given, they are always available in this simulation \- to test that the template only references variables given as arguments, produce a hash in \-\-values or the \-\-values_file, do not specify any variables that are not global, and turn on \-\-strict_variables setting\.
+.
+.IP
+If multiple templates are given, the same set of values are given to each template\. If both \-\-values and \-\-value_file are used, the \-\-values are merged on top of those given in the file\.
+.
+.IP
+When multiple templates are rendered, a separating header is output between the templates showing the name of the template before the output\. The header output can be turned off with \fB\-\-no\-header\fR\. This also concatenates the template results without any added newline separators\.
+.
+.IP
+Facts for the simulated node can be feed to the rendering process by referencing a \.yaml file with facts using the \-\-facts option\. (Values can be obtained in yaml format directly from \fBfacter\fR, or from puppet for a given node)\. Note that it is not possible to simulate the reserved variable name \fB$facts\fR in any other way\.
+.
+.IP
+Note that it is not possible to set variables using the Puppet Language that have the same names as facts as this result in an error; "attempt to redefine a variable" since facts are set first\.
+.
+.IP
+Exits with 0 if there were no validation errors\. On errors, no rendered output is produced for that template file\.
+.
+.IP
+When designing EPP templates, it is strongly recommended to define all template arguments in the template, and to give them in a hash when calling \fBepp\fR or \fBinline_epp\fR and to use as few global variables as possible, preferrably only the $facts hash\. This makes templates more free standing and are easier to reuse, and to test\.
+.
+.IP
+\fBOPTIONS\fR \fI\-\-e <source\fR> \- Render one inline epp template given on the command line\.
+.
+.IP
+\fI\-\-facts <yaml_file\fR> \- A \.yaml file containing a hash of facts made available in $facts
+.
+.IP
+\fI\-\-[no\-]header\fR \- Whether or not to show a file name header between rendered results\.
+.
+.IP
+\fI\-\-values <values_hash\fR> \- A Hash in Puppet DSL form given as arguments to the template being rendered\.
+.
+.IP
+\fI\-\-values_file <pp_or_yaml_file\fR> \- A \.pp or \.yaml file that is processed to produce a hash of values for the template\.
+.
+.IP
+\fBRETURNS\fR
+.
+.IP
+A rendered result of one or more given templates\.
+.
+.TP
+\fBvalidate\fR \- Validate the syntax of one or more EPP templates\.
+\fBSYNOPSIS\fR
+.
+.IP
+puppet epp validate [\-\-[no\-]continue_on_error] [\fItemplate\fR] [\fItemplate\fR \.\.\.]
+.
+.IP
+\fBDESCRIPTION\fR
+.
+.IP
+This action validates EPP syntax without producing any output\.
+.
+.IP
+When validating, multiple issues per file are reported up to the settings of max_error, and max_warnings\. The processing stops after having reported issues for the first encountered file with errors unless the option \-\-continue_on_error is given\.
+.
+.IP
+Files can be given using the \fBmodulename/template\.epp\fR style to lookup the template from a module, or be given as a reference to a file\. If the reference to a file can be resolved against a template in a module, the module version wins \- in this case use an absolute path to reference the template file if the module version is not wanted\.
+.
+.IP
+Exits with 0 if there were no validation errors\.
+.
+.IP
+\fBOPTIONS\fR \fI\-\-[no\-]continue_on_error\fR \- Whether or not to continue after errors are reported for a template\.
+.
+.IP
+\fBRETURNS\fR
+.
+.IP
+Nothing, or encountered syntax errors\.
+.
+.SH "EXAMPLES"
+\fBrender\fR
+.
+.P
+Render the template in module \'mymodule\' called \'mytemplate\.epp\', and give it two arguments \fBa\fR and \fBb\fR:
+.
+.IP "" 4
+.
+.nf
+
+$ puppet epp render mymodule/mytemplate\.epp \-\-values \'{a => 10, b => 20}\'
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Render a template using an absolute path:
+.
+.IP "" 4
+.
+.nf
+
+$ puppet epp render /tmp/testing/mytemplate\.epp \-\-values \'{a => 10, b => 20}\'
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Render a template with data from a \.pp file:
+.
+.IP "" 4
+.
+.nf
+
+$ puppet epp render /tmp/testing/mytemplate\.epp \-\-values_file mydata\.pp
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Render a template with data from a \.pp file and override one value on the command line:
+.
+.IP "" 4
+.
+.nf
+
+$ puppet epp render /tmp/testing/mytemplate\.epp \-\-values_file mydata\.pp \-\-values \'{a=>10}\'
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Render from STDIN:
+.
+.IP "" 4
+.
+.nf
+
+$ cat template\.epp | puppet epp render \-\-values \'{a => 10, b => 20}\'
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Set variables in a \.pp file and render a template that uses variable references:
+.
+.IP "" 4
+.
+.nf
+
+# data\.pp file
+$greeted = \'a global var\'
+undef
+
+$ puppet epp render \-e \'hello <%= $greeted %>\' \-\-values_file data\.pp
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Render a template that outputs a fact:
+.
+.IP "" 4
+.
+.nf
+
+$ facter \-\-yaml > data\.yaml
+$ puppet epp render \-e \'<% $facts[osfamily] %>\' \-\-facts data\.yaml
+.
+.fi
+.
+.IP "" 0
+.
+.P
+\fBvalidate\fR
+.
+.P
+Validate the template \'template\.epp\' in module \'mymodule\':
+.
+.IP "" 4
+.
+.nf
+
+$ puppet epp validate mymodule/template\.epp
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Validate two arbitrary template files:
+.
+.IP "" 4
+.
+.nf
+
+$ puppet epp validate mymodule/template1\.epp yourmodule/something\.epp
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Validate a template somewhere in the file system:
+.
+.IP "" 4
+.
+.nf
+
+  $ puppet epp validate /tmp/testing/template1\.epp
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Validate a template against a file relative to the current directory:
+.
+.IP "" 4
+.
+.nf
+
+ $ puppet epp validate template1\.epp
+ $ puppet epp validate \./template1\.epp
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Validate from STDIN:
+.
+.IP "" 4
+.
+.nf
+
+$ cat template\.epp | puppet epp validate
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Continue on error to see errors for all templates:
+.
+.IP "" 4
+.
+.nf
+
+$ puppet epp validate mymodule/template1\.epp mymodule/template2\.epp \-\-continue_on_error
+.
+.fi
+.
+.IP "" 0
+.
+.SH "COPYRIGHT AND LICENSE"
+Copyright 2014 by Puppet Labs Apache 2 license; see COPYING