Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

puppet-parser(8) [debian man page]

PUPPET-PARSER(8)						   Puppet manual						  PUPPET-PARSER(8)

NAME
puppet-parser - Interact directly with the parser. SYNOPSIS
puppet parser action OPTIONS
Note that any configuration parameter 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, server is a valid configuration parameter, so you can specify --server <servername> as an argument. See the configuration file documentation at http://docs.puppetlabs.com/references/stable/configuration.html for the full list of acceptable parameters. A commented list of all configuration options can also be generated by running puppet with --genconfig. --mode MODE The run mode to use for the current action. Valid modes are user, agent, and master. --render-as FORMAT The format in which to render output. The most common formats are json, s (string), yaml, and console, but other options such as dot are sometimes available. --verbose Whether to log verbosely. --debug Whether to log debug information. ACTIONS
validate - Validate the syntax of one or more Puppet manifests. SYNOPSIS puppet parser validate [manifest] [manifest ...] DESCRIPTION This action validates Puppet DSL syntax without compiling a catalog or syncing any resources. If no manifest files are provided, it will validate the default site manifest. RETURNS Nothing, or the first syntax error encountered. EXAMPLES
validate Validate the default site manifest at /etc/puppet/manifests/site.pp: $ puppet parser validate Validate two arbitrary manifest files: $ puppet parser validate init.pp vhost.pp COPYRIGHT AND LICENSE
Copyright 2011 by Puppet Labs Apache 2 license; see COPYING Puppet Labs, LLC June 2012 PUPPET-PARSER(8)

Check Out this Related Man Page

PUPPET-CONFIG(8)						   Puppet manual						  PUPPET-CONFIG(8)

NAME
puppet-config - Interact with Puppet's configuration options. SYNOPSIS
puppet config action OPTIONS
Note that any configuration parameter 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, server is a valid configuration parameter, so you can specify --server <servername> as an argument. See the configuration file documentation at http://docs.puppetlabs.com/references/stable/configuration.html for the full list of acceptable parameters. A commented list of all configuration options can also be generated by running puppet with --genconfig. --mode MODE The run mode to use for the current action. Valid modes are user, agent, and master. --render-as FORMAT The format in which to render output. The most common formats are json, s (string), yaml, and console, but other options such as dot are sometimes available. --verbose Whether to log verbosely. --debug Whether to log debug information. ACTIONS
print - Examine Puppet's current configuration settings. SYNOPSIS puppet config print (all | setting [setting ...] DESCRIPTION Prints the value of a single configuration option or a list of configuration options. This action is an alternate interface to the information available with puppet <subcommand> --configprint. RETURNS A single value when called with one config setting, and a list of settings and values when called with multiple options or "all." NOTES By default, this action reads the configuration in agent mode. Use the '--mode' and '--environment' flags to examine other configu- ration domains. EXAMPLES
print Get puppet's runfile directory: $ puppet config print rundir Get a list of important directories from the master's config: $ puppet config print all --mode master | grep -E "(path|dir)" COPYRIGHT AND LICENSE
Copyright 2011 by Puppet Labs Apache 2 license; see COPYING Puppet Labs, LLC June 2012 PUPPET-CONFIG(8)
Man Page