5
# Run a stand-alone +puppet+ manifest.
9
# puppet apply [-h|--help] [-V|--version] [-d|--debug] [-v|--verbose] [-e|--execute]
10
# [--detailed-exitcodes] [-l|--logdest <file>] [--apply catalog] <file>
14
# This is the standalone puppet execution tool; use it to execute
15
# individual manifests that you write. If you need to execute site-wide
16
# manifests, use 'puppet agent' and 'puppet master'.
20
# Note that any configuration parameter that's valid in the configuration file
21
# is also a valid long argument. For example, 'ssldir' is a valid configuration
22
# parameter, so you can specify '--ssldir <directory>' as an argument.
24
# See the configuration file documentation at
25
# http://docs.puppetlabs.com/references/stable/configuration.html for
26
# the full list of acceptable parameters. A commented list of all
27
# configuration options can also be generated by running puppet with
31
# Enable full debugging.
33
# detailed-exitcodes::
34
# Provide transaction information via exit codes. If this is enabled, an exit
35
# code of '2' means there were changes, and an exit code of '4' means that there
36
# were failures during the transaction.
39
# Print this help message
42
# Load any stored classes. 'puppet agent' caches configured classes (usually at
43
# /etc/puppet/classes.txt), and setting this option causes all of those classes
44
# to be set in your puppet manifest.
47
# Where to send messages. Choose between syslog, the console, and a log file.
48
# Defaults to sending messages to the console.
51
# Execute a specific piece of Puppet code
54
# Print extra information.
57
# Capability to apply JSON catalog (such as one generated with --compile on the Puppet master).
58
# You can either specify a JSON catalog file or pipe in JSON from standard input.
62
# puppet -l /tmp/manifest.log manifest.pp
70
# Copyright (c) 2005 Puppet Labs, LLC
71
# Licensed under the GNU Public License
73
#Puppet::Application[:apply].run