hiera(1) [debian man page]

HIERA(1)							       Utils								  HIERA(1)

NAME

       hiera - Lightweight Pluggable Hierarchical Database

SYNOPSIS

       hiera [options]

DESCRIPTION

       hiera is a simple pluggable hierarchical database.

OPTIONS

       Mandatory arguments to long options are mandatory for short options too.

       -V, --version
	      Version information

       -d, --debug
	      Show debugging information

       -a, --array
	      Array search

       -h, --hash
	      Hash search

       -c, --config CONFIG
	      Configuration file

       -j, --json SCOPE
	      JSON format file to load scope from

       -y, --yaml SCOPE
	      YAML format file to load scope from

       -m, --mcollective IDENTITY
	      Retrieve facts from a node via mcollective as scope

       -i, --inventory_service IDENTITY Retrieve facts for a node via Puppet's inventory service as scope

AUTHORS

       hiera is a part of Puppet Hiera and developed by Puppet Labs <info@puppetlabs.com>, (R.I.Pienaar <rip@devco.net> respectively).

       This man page was written by Patrick Ringl <patrick_@freenet.de> for the Debian GNU/Linux distribution (but it may also be used by others).

hiera								       2012								  HIERA(1)

PUPPET-SECRET_AGENT(8)						   Puppet manual					    PUPPET-SECRET_AGENT(8)

NAME

       puppet-secret_agent - Mimics puppet agent.

SYNOPSIS

       puppet secret_agent action

DESCRIPTION

       This subcommand currently functions as a proof of concept, demonstrating how the Faces API exposes Puppet's internal systems to application
       logic; compare the actual code for puppet agent. It will eventually replace puppet agent entirely, and can provide a template for users who
       wish to implement agent-like functionality with non-standard application logic.

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

       synchronize - Run secret_agent once.
	      SYNOPSIS

	      puppet secret_agent

	      DESCRIPTION

	      Mimics  a single run of puppet agent. This action does not currently daemonize, but can download plugins, submit facts, retrieve and
	      apply a catalog, and submit a report to the puppet master.

	      RETURNS

	      Verbose logging from the completed run. When used from the Ruby API: returns a Puppet::Transaction::Report object.

	      NOTES

	      This action requires that the puppet master's auth.conf file allow save access to the facts REST terminus. Puppet agent does not use
	      this facility, and it is turned off by default. See http://docs.puppetlabs.com/guides/rest_auth_conf.html for more details.

EXAMPLES

       synchronize

       Trigger a Puppet run with the configured puppet master:

       $ puppet secret_agent

COPYRIGHT AND LICENSE

       Copyright 2011 by Puppet Labs Apache 2 license; see COPYING

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