puppet-plugin(8) [debian man page]

PUPPET-PLUGIN(8)						   Puppet manual						  PUPPET-PLUGIN(8)

NAME

       puppet-plugin - Interact with the Puppet plugin system.

SYNOPSIS

       puppet plugin action

DESCRIPTION

       This subcommand provides network access to the puppet master's store of plugins.

       The  puppet  master  serves Ruby code collected from the lib directories of its modules. These plugins can be used on agent nodes to extend
       Facter and implement custom types and providers. Plugins are normally downloaded by puppet agent during the course of a run.

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

       download - Download plugins from the puppet master.
	      SYNOPSIS

	      puppet plugin download

	      DESCRIPTION

	      Downloads plugins from the configured puppet master. Any plugins downloaded in this way will be used in all subsequent Puppet activ-
	      ity. This action modifies files on disk.

	      RETURNS

	      A list of the files downloaded, or a confirmation that no files were downloaded. When used from the Ruby API, this action returns an
	      array of the files downloaded, which will be empty if none were retrieved.

EXAMPLES

       download

       Retrieve plugins from the puppet master:

       $ puppet plugin download

       Retrieve plugins from the puppet master (API example):

       $ Puppet::Face[:plugin, '0.0.1'].download

COPYRIGHT AND LICENSE

       Copyright 2011 by Puppet Labs Apache 2 license; see COPYING

Puppet Labs, LLC						     June 2012							  PUPPET-PLUGIN(8)

PUPPET-APPLY(8) 						   Puppet manual						   PUPPET-APPLY(8)

NAME

       puppet-apply - Apply Puppet manifests locally

SYNOPSIS

       Applies a standalone Puppet manifest to the local system.

USAGE

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

DESCRIPTION

       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.

OPTIONS

       Note that any configuration parameter that's valid in the configuration file is also a valid long argument. For example, 'modulepath' is  a
       valid configuration parameter, so you can specify '--tags class,tag' 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'.

       --debug
	      Enable full debugging.

       --detailed-exitcodes
	      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 failures.

       --help Print this help message

       --loadclasses
	      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.

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

       --execute
	      Execute a specific piece of Puppet code

       --verbose
	      Print extra information.

       --apply
	      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. Deprecated, please use --catalog instead.

       --catalog
	      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.

EXAMPLE

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

AUTHOR

       Luke Kanies

COPYRIGHT

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

Puppet Labs, LLC						     June 2012							   PUPPET-APPLY(8)