Provided by: puppet-common_3.8.5-2_all bug


       puppet-apply - Apply Puppet manifests locally


       Applies a standalone Puppet manifest to the local system.


       puppet   apply   [-h|--help]  [-V|--version]  [-d|--debug]  [-v|--verbose]  [-e|--execute]
       [--detailed-exitcodes] [-l|--logdest file] [--noop] [--catalog catalog] file


       This is the standalone puppet execution tool; use it to apply individual manifests.

       When provided with a modulepath, via  command  line  or  config  file,  puppet  apply  can
       effectively  mimic  the  catalog  that would be served by puppet master with access to the
       same modules, although there are some subtle differences. When  combined  with  scheduling
       and  an automated system for pushing manifests, this can be used to implement a serverless
       Puppet site.

       Most users should use ´puppet agent´ and ´puppet master´ for site-wide manifests.


       Note that any configuration parameter that´s valid in the configuration  file  is  also  a
       valid  long  argument.  For example, ´tags´ is a valid configuration parameter, so you can
       specify ´--tags class,tag´ as an argument.

       See          the          configuration          file           documentation           at   for  the  full  list  of
       acceptable parameters. A commented list of all configuration options can also be generated
       by running puppet with ´--genconfig´.

              Enable full debugging.

              Provide transaction information via exit codes. If this is enabled, an exit code of
              ´2´ means there were changes, an exit code of ´4´ means there were failures  during
              the  transaction,  and  an  exit  code  of  ´6´  means  there were both changes and

       --help Print this help message

              Load any stored classes. ´puppet  agent´  caches  configured  classes  (usually  at
              /etc/puppet/classes.txt), and setting this option causes all of those classes to be
              set in your puppet manifest.

              Where to send messages. Choose  between  syslog,  the  console,  and  a  log  file.
              Defaults to sending messages to the console.

       --noop Use  ´noop´  mode  where Puppet runs in a no-op or dry-run mode. This is useful for
              seeing what changes Puppet will make without actually executing the changes.

              Execute a specific piece of Puppet code

              Print extra information.

              Apply a JSON catalog (such as one generated with ´puppet  master  --compile´).  You
              can either specify a JSON file or pipe in JSON from standard input.


       $ puppet apply -l /tmp/manifest.log manifest.pp
       $ puppet apply --modulepath=/root/dev/modules -e "include ntpd::server"
       $ puppet apply --catalog catalog.json


       Luke Kanies


       Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2.0 License