openvox 7.37.1 → 8.19.0

data/man/man8/puppet-device.8

@@ -1,119 +1,83 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "PUPPET\-DEVICE" "8" "October 2024" "Puppet, Inc." "Puppet manual"
-.
+.\" generated with Ronn-NG/v0.10.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.10.1
+.TH "PUPPET\-DEVICE" "8" "January 2025" "Vox Pupuli" "OpenVox manual"
 .SH "NAME"
-\fBpuppet\-device\fR \- Manage remote network devices
-.
+\fBpuppet\-device\fR \- Manage remote network devices via OpenVox
 .SH "SYNOPSIS"
-Retrieves catalogs from the Puppet master and applies them to remote devices\.
-.
+Retrieves catalogs from the OpenVox server and applies them to remote devices\.
 .P
 This subcommand can be run manually; or periodically using cron, a scheduled task, or a similar tool\.
-.
 .SH "USAGE"
 puppet device [\-h|\-\-help] [\-v|\-\-verbose] [\-d|\-\-debug] [\-l|\-\-logdest syslog|\fIfile\fR|console] [\-\-detailed\-exitcodes] [\-\-deviceconfig \fIfile\fR] [\-w|\-\-waitforcert \fIseconds\fR] [\-\-libdir \fIdirectory\fR] [\-a|\-\-apply \fIfile\fR] [\-f|\-\-facts] [\-r|\-\-resource \fItype\fR [name]] [\-t|\-\-target \fIdevice\fR] [\-\-user=\fIuser\fR] [\-V|\-\-version]
-.
 .SH "DESCRIPTION"
-Devices require a proxy Puppet agent to request certificates, collect facts, retrieve and apply catalogs, and store reports\.
-.
+Devices require a proxy OpenVox agent to request certificates, collect facts, retrieve and apply catalogs, and store reports\.
 .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\.
-.
+Devices managed by the puppet\-device subcommand on an OpenVox agent are configured in device\.conf, which is located at $confdir/device\.conf by default, and is configurable with the $deviceconfig setting\.
 .P
 The device\.conf file is an INI\-like file, with one section per device:
-.
 .P
 [\fIDEVICE_CERTNAME\fR] type \fITYPE\fR url \fIURL\fR debug
-.
 .P
 The section name specifies the certname of the device\.
-.
 .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://puppet\.com/docs/puppet/latest/config_file_device\.html for details\.
-.
 .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\.
-.
+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
 \-\-help, \-h
 Print this help message
-.
 .TP
 \-\-verbose, \-v
 Turn on verbose reporting\.
-.
 .TP
 \-\-debug, \-d
 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'\. Multiple destinations can be set using a comma separated list (eg: \fB/path/file1,console,/path/file2\fR)"
 .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\.
-.
+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
 \-\-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 preceding exit codes happened\.
-.
+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 preceding exit codes happened\.
 .TP
 \-\-deviceconfig
 Path to the device config file for puppet device\. Default: $confdir/device\.conf
-.
 .TP
 \-\-waitforcert, \-w
 This option only matters for targets that do not yet have certificates and it is enabled by default, with a value of 120 (seconds)\. This causes +puppet device+ to poll the server every 2 minutes and ask it to sign a certificate request\. This is useful for the initial setup of a target\. You can turn off waiting for certificates by specifying a time of 0\.
-.
 .TP
 \-\-libdir
 Override the per\-device libdir with a local directory\. Specifying a libdir also disables pluginsync\. This is useful for testing\.
-.
 .IP
-A path ending with \'\.jsonl\' will receive structured output in JSON Lines format\.
-.
+A path ending with '\.jsonl' will receive structured output in JSON Lines format\.
 .TP
 \-\-apply
 Apply a manifest against a remote target\. Target must be specified\.
-.
 .TP
 \-\-facts
 Displays the facts of a remote target\. Target must be specified\.
-.
 .TP
 \-\-resource
 Displays a resource state as Puppet code, roughly equivalent to \fBpuppet resource\fR\. Can be filtered 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\.
-.
 .SH "EXAMPLE"
-.
 .nf
-
   $ puppet device \-\-target remotehost \-\-verbose
-.
 .fi
-.
 .SH "AUTHOR"
 Brice Figureau
-.
 .SH "COPYRIGHT"
-Copyright (c) 2011\-2018 Puppet Inc\., LLC Licensed under the Apache 2\.0 License
+Copyright (c) 2011\-2018 Puppet Inc\., Copyright (c) 2024 Vox Pupuli Licensed under the Apache 2\.0 License

data/man/man8/puppet-doc.8

@@ -1,46 +1,30 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "PUPPET\-DOC" "8" "October 2024" "Puppet, Inc." "Puppet manual"
-.
+.\" generated with Ronn-NG/v0.10.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.10.1
+.TH "PUPPET\-DOC" "8" "January 2025" "Vox Pupuli" "OpenVox manual"
 .SH "NAME"
-\fBpuppet\-doc\fR \- Generate Puppet references
-.
+\fBpuppet\-doc\fR \- Generate Puppet references for OpenVox
 .SH "SYNOPSIS"
-Generates a reference for all Puppet types\. Largely meant for internal Puppet Inc\. use\. (Deprecated)
-.
+Generates a reference for all Puppet types\. Largely meant for internal 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 Inc\. web site\.
-.
+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 documents which can be posted to a website\.
 .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\'\.
-.
+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 Inc\., LLC Licensed under the Apache 2\.0 License
+Copyright (c) 2011 Puppet Inc\. Copyright (c) 2024 Vox Pupuli Licensed under the Apache 2\.0 License

data/man/man8/puppet-epp.8

@@ -1,377 +1,232 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "PUPPET\-EPP" "8" "October 2024" "Puppet, Inc." "Puppet manual"
-.
+.\" generated with Ronn-NG/v0.10.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.10.1
+.TH "PUPPET\-EPP" "8" "January 2025" "Vox Pupuli" "OpenVox 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\.
-.
+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://puppet\.com/docs/puppet/latest/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"
-.
 .IP "\(bu" 4
 \fBdump\fR \- Outputs a dump of the internal template parse tree for debugging: \fBSYNOPSIS\fR
-.
 .IP
-puppet epp dump [\-\-e \fIsource\fR] [\-\-[no\-]validate] [\-\-format \fIold, pn, or json\fR] [\-\-pretty] [\-\-[no\-]header] [\-\-format \fIold|pn|json\fR] [\-\-pretty] { \-e \fIsource\fR | [\fItemplates\fR \.\.\.] }
-.
+puppet epp dump [\-\-e \fIsource\fR] [\-\-[no\-]validate] [\-\-format \fIold, pn, or json\fR] [\-\-pretty] [\-\-[no\-]header] [\-\-format \fIold|pn|json\fR] [\-\-pretty] { \-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\.
-.
 .IP
 The output format can be controlled using the \-\-format \fIold|pn|json\fR where:
-.
 .IP "\(bu" 4
-\'old\' is the default, but now deprecated format which is not API\.
-.
+\&'old' is the default, but now deprecated format which is not API\.
 .IP "\(bu" 4
-\'pn\' is the Puppet Extended S\-Expression Notation\.
-.
+\&'pn' is the Puppet Extended S\-Expression Notation\.
 .IP "\(bu" 4
-\'json\' outputs the same graph as \'pn\' but with JSON syntax\.
-.
+\&'json' outputs the same graph as 'pn' but with JSON syntax\.
 .IP "" 0
-.
 .IP
-The output will be "pretty printed" when the option \-\-pretty is given together with \-\-format \'pn\' or \'json\'\. This option has no effect on the \'old\' format\.
-.
+The output will be "pretty printed" when the option \-\-pretty is given together with \-\-format 'pn' or 'json'\. This option has no effect on the 'old' format\.
 .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 suppressed with the option \-\-no\-header\. The option \-\-[no\-]header has no effect when a single template is dumped\.
-.
 .IP
 When debugging the epp parser itself, it may be useful to suppress the validation 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\-\-format <old, pn, or json\fR> \- Get result in \'old\' (deprecated format), \'pn\' (new format), or \'json\' (new format in JSON)\.
-.
+\fI\-\-format <old, pn, or json\fR> \- Get result in 'old' (deprecated format), 'pn' (new format), or 'json' (new format in JSON)\.
 .IP
 \fI\-\-[no\-]header\fR \- Whether or not to show a file name header between files\.
-.
 .IP
 \fI\-\-pretty\fR \- Pretty print output\. Only applicable together with \-\-format pn or json
-.
 .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\.
-.
 .IP "\(bu" 4
 \fBrender\fR \- Renders an epp template as text: \fBSYNOPSIS\fR
-.
 .IP
-puppet epp render [\-\-node \fInode_name\fR] [\-\-e \fIsource\fR] [\-\-values \fIvalues_hash\fR] [\-\-values_file \fIpp_or_yaml_file\fR] [\-\-facts \fIfacts_file\fR] [\-\-[no\-]header] \-e \fIsource\fR | [\fItemplates\fR \.\.\.]
-.
+puppet epp render [\-\-node \fInode_name\fR] [\-\-e \fIsource\fR] [\-\-values \fIvalues_hash\fR] [\-\-values_file \fIpp_or_yaml_file\fR] [\-\-facts \fIfacts_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\.
-.
+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 from the node where the command is being run are used by default\.args Facts can be obtained for other nodes if they have called in, and reported their facts by using the \fB\-\-node <nodename>\fR flag\.
-.
 .IP
 Overriding node facts as well as additional facts can be given in a \.yaml or \.json file and referencing it with 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, preferably 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 <facts_file\fR> \- A \.yaml or \.json file containing a hash of facts made available in $facts and $trusted
-.
 .IP
 \fI\-\-[no\-]header\fR \- Whether or not to show a file name header between rendered results\.
-.
 .IP
 \fI\-\-node <node_name\fR> \- The name of the node for which facts are obtained\. Defaults to facts for the local node\.
-.
 .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\.
-.
 .IP "\(bu" 4
 \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 \.\.\.]
-.
+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\.
-.
 .IP "" 0
-.
 .SH "EXAMPLES"
 \fBrender\fR
-.
 .P
-Render the template in module \'mymodule\' called \'mytemplate\.epp\', and give it two arguments \fBa\fR and \fBb\fR:
-.
+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}\'
-.
+$ 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}\'
-.
+$ 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}\'
-.
+$ 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}\'
-.
+$ 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\'
+$greeted = 'a global var'
 undef
 
-$ puppet epp render \-e \'hello <%= $greeted %>\' \-\-values_file data\.pp
-.
+$ 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
-.
+$ puppet epp render \-e '<% $facts[osfamily] %>' \-\-facts data\.yaml
 .fi
-.
 .IP "" 0
-.
 .P
 \fBvalidate\fR
-.
 .P
-Validate the template \'template\.epp\' in module \'mymodule\':
-.
+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 Inc\. Apache 2 license; see COPYING
+Copyright 2014 by Puppet Inc\., Vox Pupuli Apache 2 license; see COPYING