![]() ![]() ![]() When used from the API, returns an array of Puppet::Resource objects excised from a catalog. RETURNS A list of resource references ("Type"). SYNOPSIS puppet catalog select host resource_type DESCRIPTION Retrieves a catalog for the specified host, then searches it for all resources of the requested type. Select - Retrieve a catalog and filter it for resources of a given type. SYNOPSIS puppet catalog search query DESCRIPTION Invalid for this subcommand. As the Faces framework does not currently accept data from STDIN, save actions cannot currently be invoked from SYNOPSIS puppet catalog save key DESCRIPTION API only: create or overwrite an object. Save - API only: create or overwrite an object. Note that different run modes may have different default termini when in doubt, specify the run SYNOPSIS puppet catalog info ĭESCRIPTION Prints the default terminus class for this subcommand. Info - Print the default terminus class for this face. When used from the Ruby API, returns a Puppet::Resource::Catalog object. SYNOPSIS puppet catalog find certname DESCRIPTION Retrieve the catalog for a node. The terminus mustīe explicitly re-set for subsequent catalog actions. NOTES When used from the Ruby API, this action has a side effect of leaving Puppet::Resource::_class set to yaml. The saved catalog can be used in any subsequent catalog action by specifying '-terminus yaml' for that action. This action always contacts the puppet master and will ignore alternate SYNOPSIS puppet catalog download ĭESCRIPTION Retrieves a catalog from the puppet master and saves it to the local yaml cache. SYNOPSIS puppet catalog destroy key DESCRIPTION Invalid for this subcommand.ĭownload - Download this node's catalog from the puppet master server. When used from the Ruby API, returns a Puppet::Transaction::Report object. ![]() This action takes no arguments, but the source of the catalog can be managed with the -terminus option. SYNOPSIS puppet catalog apply ĭESCRIPTION Finds and applies a catalog. Actions apply - Find and apply a catalog. See the "Notes" section of this face's manpage for The terminus for an action is often determined by context, but occasionally needs to be set explicitly. Various local data models, which are in turn used by the indirected subsystem on the puppet master whenever it receives a remote request. Most of them have additional terminuses for In Puppet parlance, these backends areĪlmost all indirected subsystems have a rest terminus that interacts with the puppet master's data. These subsystems are each able to retrieve and alter a specific type of data (with the familiarĪctions of find, search, save, and destroy) from an arbitrary number of pluggable backends. Indirector faces expose indirected subsystems of Puppet. The most common formats are json, s (string), yaml, and console, but other options suchĪ terminus can take additional arguments to refine the operation, which are passed as an arbitrary hash to the back-end. The run mode to use for the current action. A commented list of all configuration options can also be generated by running puppet with -genconfig. See the configuration file documentation at for the full list of acceptable For example, server is a valid configuration parameter, so you can specify Note that any configuration parameter that's valid in the configuration file is also a valid longĪrgument, although it may or may not be relevant to the present action. OmniGraffle or Graphviz) with '-render-as dot'. You can also choose to print any catalog in 'dot' format (for easy graph viewing with By default, it interacts with the compiling subsystem and compiles a catalog using the default manifest and certname, but you canĬhange the source of the catalog with the -terminus option. This subcommand deals with catalogs, which are compiled per-node artifacts generated from a set ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |