puppet 4.10.12 → 5.0.0

data/lib/semver.rb

@@ -1,146 +0,0 @@
-require 'puppet/util/monkey_patches'
-
-# We need to subclass Numeric to force range comparisons not to try to iterate over SemVer
-# and instead use numeric comparisons (eg >, <, >=, <=)
-# @api private
-# @deprecated
-class SemVer < Numeric
-  include Comparable
-
-  VERSION = /^v?(\d+)\.(\d+)\.(\d+)(-[0-9A-Za-z-]*|)$/
-  SIMPLE_RANGE = /^v?(\d+|[xX])(?:\.(\d+|[xX])(?:\.(\d+|[xX]))?)?$/
-
-  def self.valid?(ver)
-    VERSION =~ ver
-  end
-
-  def self.find_matching(pattern, versions)
-    versions.select { |v| v.matched_by?("#{pattern}") }.sort.last
-  end
-
-  def self.pre(vstring)
-    vstring =~ /-/ ? vstring : vstring + '-'
-  end
-
-  def self.[](range, suppress_deprecation_warning = false)
-    range.gsub(/([><=])\s+/, '\1').split(/\b\s+(?!-)/).map do |r|
-      case r
-      when SemVer::VERSION
-        SemVer.new(pre(r), suppress_deprecation_warning) .. SemVer.new(r, suppress_deprecation_warning)
-      when SemVer::SIMPLE_RANGE
-        r += ".0" unless SemVer.valid?(r.gsub(/x/i, '0'))
-        SemVer.new(r.gsub(/x/i, '0'), suppress_deprecation_warning)...SemVer.new(r.gsub(/(\d+)\.x/i) { "#{$1.to_i + 1}.0" } + '-', suppress_deprecation_warning)
-      when /\s+-\s+/
-        a, b = r.split(/\s+-\s+/)
-        SemVer.new(pre(a), suppress_deprecation_warning) .. SemVer.new(b, suppress_deprecation_warning)
-      when /^~/
-        ver = r.sub(/~/, '').split('.').map(&:to_i)
-        start = (ver + [0] * (3 - ver.length)).join('.')
-
-        ver.pop unless ver.length == 1
-        ver[-1] = ver.last + 1
-
-        finish = (ver + [0] * (3 - ver.length)).join('.')
-        SemVer.new(pre(start), suppress_deprecation_warning) ... SemVer.new(pre(finish), suppress_deprecation_warning)
-      when /^>=/
-        ver = r.sub(/^>=/, '')
-        SemVer.new(pre(ver), suppress_deprecation_warning) .. SemVer::MAX
-      when /^<=/
-        ver = r.sub(/^<=/, '')
-        SemVer::MIN .. SemVer.new(ver, suppress_deprecation_warning)
-      when /^>/
-        if r =~ /-/
-          ver = [r[1..-1]]
-        else
-          ver = r.sub(/^>/, '').split('.').map(&:to_i)
-          ver[2] = ver.last + 1
-        end
-        SemVer.new(ver.join('.') + '-', suppress_deprecation_warning) .. SemVer::MAX
-      when /^</
-        ver = r.sub(/^</, '')
-        SemVer::MIN ... SemVer.new(pre(ver), suppress_deprecation_warning)
-      else
-        (1..1)
-      end
-    end.inject { |a,e| a & e }
-  end
-
-  attr_reader :major, :minor, :tiny, :special
-
-  def initialize(ver, suppress_deprecation_warning = false)
-    unless suppress_deprecation_warning || Puppet[:strict] == :off
-      Puppet.warn_once(:deprecation, 'Puppet::SemVer',
-        "Use of class Puppet::SemVer is deprecated. SemanticPuppet::Version or SemanticPuppet::VersionRange should be used instead")
-    end
-
-    unless SemVer.valid?(ver)
-      raise ArgumentError.new("Invalid version string '#{ver}'!")
-    end
-
-    @major, @minor, @tiny, @special = VERSION.match(ver).captures.map do |x|
-      # Because Kernel#Integer tries to interpret hex and octal strings, which
-      # we specifically do not want, and which cannot be overridden in 1.8.7.
-      Float(x).to_i rescue x
-    end
-  end
-
-  def <=>(other)
-    # Note that prior to ruby 2.3.0, if a <=> method threw an exception, ruby
-    # would silently rescue the exception and return nil from <=> (which causes
-    # the derived == comparison to return false). Starting in ruby 2.3.0, this
-    # behavior changed and the exception is actually thrown. Some comments at:
-    # https://bugs.ruby-lang.org/issues/7688
-    #
-    # SemVer#initialize above throws an ArgumentError given an invalid
-    # version string. So, to preserve the ability to use the == operator
-    # between a SemVer object and an invalid version string, we take care here
-    # to do the valid? check before constructing the SemVer object (i.e.
-    # so that a == comparison doesn't throw an exception, but just returns
-    # false.)
-    unless other.is_a? SemVer
-      return nil unless SemVer.valid?(other)
-      other = SemVer.new("#{other}")
-    end
-
-    return self.major <=> other.major unless self.major == other.major
-    return self.minor <=> other.minor unless self.minor == other.minor
-    return self.tiny  <=> other.tiny  unless self.tiny  == other.tiny
-
-    return 0  if self.special  == other.special
-    return 1  if self.special  == ''
-    return -1 if other.special == ''
-
-    return self.special <=> other.special
-  end
-
-  def matched_by?(pattern)
-    # For the time being, this is restricted to exact version matches and
-    # simple range patterns.  In the future, we should implement some or all of
-    # the comparison operators here:
-    # https://github.com/isaacs/node-semver/blob/d474801/semver.js#L340
-
-    case pattern
-    when SIMPLE_RANGE
-      pattern = SIMPLE_RANGE.match(pattern).captures
-      pattern[1] = @minor unless pattern[1] && pattern[1] !~ /x/i
-      pattern[2] = @tiny  unless pattern[2] && pattern[2] !~ /x/i
-      [@major, @minor, @tiny] == pattern.map { |x| x.to_i }
-    when VERSION
-      self == SemVer.new(pattern)
-    else
-      false
-    end
-  end
-
-  def inspect
-    @vstring || "v#{@major}.#{@minor}.#{@tiny}#{@special}"
-  end
-  alias :to_s :inspect
-
-  MIN = SemVer.new('0.0.0-', true)
-  MIN.instance_variable_set(:@vstring, 'vMIN')
-
-  MAX = SemVer.new('8.0.0', true)
-  MAX.instance_variable_set(:@major, Float::INFINITY) # => Infinity
-  MAX.instance_variable_set(:@vstring, 'vMAX')
-end

data/man/man8/extlookup2hiera.8

@@ -1,10 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "EXTLOOKUP2HIERA" "8" "May 2018" "Puppet, Inc." "Puppet manual"
-.
-.SH "NAME"
-\fBextlookup2hiera\fR
-.
-.P
-Converter for extlookup CSV files into Hiera JSON and YAML files \-i, \-\-in FILE Input CSV file \-o, \-\-out FILE Output Hiera file \-j, \-\-json Create JSON format file

data/man/man8/puppet-file.8

@@ -1,189 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "PUPPET\-FILE" "8" "May 2018" "Puppet, Inc." "Puppet manual"
-.
-.SH "NAME"
-\fBpuppet\-file\fR \- Retrieve and store files in a filebucket
-.
-.SH "SYNOPSIS"
-puppet file \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra HASH]
-.
-.SH "DESCRIPTION"
-This subcommand interacts with objects stored in a local or remote filebucket\. File objects are accessed by their MD5 sum; see the examples for the relevant syntax\.
-.
-.SH "OPTIONS"
-Note that any setting 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, \fBserver\fR and \fBrun_mode\fR are valid settings, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
-.
-.P
-See the configuration file documentation at \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
-.
-.TP
-\-\-render\-as FORMAT
-The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
-.
-.TP
-\-\-verbose
-Whether to log verbosely\.
-.
-.TP
-\-\-debug
-Whether to log debug information\.
-.
-.TP
-\-\-extra HASH
-A terminus can take additional arguments to refine the operation, which are passed as an arbitrary hash to the back\-end\. Anything passed as the extra value is just send direct to the back\-end\.
-.
-.TP
-\-\-terminus TERMINUS
-Indirector faces expose indirected subsystems of Puppet\. These subsystems are each able to retrieve and alter a specific type of data (with the familiar actions of \fBfind\fR, \fBsearch\fR, \fBsave\fR, and \fBdestroy\fR) from an arbitrary number of pluggable backends\. In Puppet parlance, these backends are called terminuses\.
-.
-.IP
-Almost all indirected subsystems have a \fBrest\fR terminus that interacts with the puppet master\'s data\. Most of them have additional terminuses for various local data models, which are in turn used by the indirected subsystem on the puppet master whenever it receives a remote request\.
-.
-.IP
-The terminus for an action is often determined by context, but occasionally needs to be set explicitly\. See the "Notes" section of this face\'s manpage for more details\.
-.
-.SH "ACTIONS"
-.
-.TP
-\fBdownload\fR \- Download a file into the local filebucket\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet file download [\-\-terminus TERMINUS] [\-\-extra HASH] ( {md5}\fIchecksum\fR | \fIpuppet_url\fR )
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-Downloads a file from the puppet master\'s filebucket and duplicates it in the local filebucket\. This action\'s checksum syntax differs from \fBfind\fR\'s, and it can accept a <puppet:///> URL\.
-.
-.IP
-\fBRETURNS\fR
-.
-.IP
-Nothing\.
-.
-.TP
-\fBfind\fR \- Retrieve a file from the filebucket\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet file find [\-\-terminus TERMINUS] [\-\-extra HASH] md5/\fImd5sum\fR
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-Retrieve a file from the filebucket\.
-.
-.IP
-\fBRETURNS\fR
-.
-.IP
-The file object with the specified checksum\.
-.
-.IP
-RENDERING ISSUES: Rendering as a string returns the contents of the file object; rendering as yaml returns a hash of metadata about said file, including but not limited to its contents\. Rendering as json is currently broken, and returns a hash containing only the contents of the file\.
-.
-.TP
-\fBinfo\fR \- Print the default terminus class for this face\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet file info [\-\-terminus TERMINUS] [\-\-extra HASH]
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
-.
-.TP
-\fBsave\fR \- API only: create or overwrite an object\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet file save [\-\-terminus TERMINUS] [\-\-extra HASH] \fIkey\fR
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-API only: create or overwrite an object\. As the Faces framework does not currently accept data from STDIN, save actions cannot currently be invoked from the command line\.
-.
-.TP
-\fBstore\fR \- Store a file in the local filebucket\.
-\fBSYNOPSIS\fR
-.
-.IP
-puppet file store [\-\-terminus TERMINUS] [\-\-extra HASH] \fIfile\fR
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-Store a file in the local filebucket\.
-.
-.IP
-\fBRETURNS\fR
-.
-.IP
-Nothing\.
-.
-.SH "EXAMPLES"
-\fBdownload\fR
-.
-.P
-Download a file by URL:
-.
-.P
-$ puppet file download puppet:///modules/editors/vim/\.vimrc
-.
-.P
-Download a file by MD5 sum:
-.
-.P
-$ puppet file download {md5}8f798d4e754db0ac89186bbaeaf0af18
-.
-.P
-\fBfind\fR
-.
-.P
-Retrieve the contents of a file:
-.
-.P
-$ puppet file find md5/9aedba7f413c97dc65895b1cd9421f2c \-\-render\-as s
-.
-.P
-\fBstore\fR
-.
-.P
-Store a file:
-.
-.P
-$ puppet file store /root/\.bashrc
-.
-.SH "NOTES"
-To retrieve the unmunged contents of a file, you must call find with \-\-render\-as s\. Rendering as yaml will return a hash of metadata about the file, including its contents\.
-.
-.P
-This subcommand does not interact with the \fBclientbucketdir\fR (the default local filebucket for puppet agent); it interacts with the primary "master"\-type filebucket located in the \fBbucketdir\fR\. If you wish to interact with puppet agent\'s default filebucket, you\'ll need to set the \fI\-\-bucketdir\fR option appropriately when invoking actions\.
-.
-.P
-This subcommand is an indirector face, which exposes \fBfind\fR, \fBsearch\fR, \fBsave\fR, and \fBdestroy\fR actions for an indirected subsystem of Puppet\. Valid termini for this face include:
-.
-.IP "\(bu" 4
-\fBfile\fR
-.
-.IP "\(bu" 4
-\fBrest\fR
-.
-.IP "\(bu" 4
-\fBselector\fR
-.
-.IP "" 0
-.
-.SH "COPYRIGHT AND LICENSE"
-Copyright 2011 by Puppet Inc\. Apache 2 license; see COPYING

data/man/man8/puppet-generate.8

@@ -1,84 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "PUPPET\-GENERATE" "8" "May 2018" "Puppet, Inc." "Puppet manual"
-.
-.SH "NAME"
-\fBpuppet\-generate\fR \- Generates Puppet code from Ruby definitions\.
-.
-.SH "SYNOPSIS"
-puppet generate \fIaction\fR
-.
-.SH "OPTIONS"
-Note that any setting 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, \fBserver\fR and \fBrun_mode\fR are valid settings, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
-.
-.P
-See the configuration file documentation at \fIhttps://docs\.puppetlabs\.com/puppet/latest/reference/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
-.
-.TP
-\-\-render\-as FORMAT
-The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
-.
-.TP
-\-\-verbose
-Whether to log verbosely\.
-.
-.TP
-\-\-debug
-Whether to log debug information\.
-.
-.SH "ACTIONS"
-.
-.TP
-\fBtypes\fR \- Generates Puppet code for custom types
-\fBSYNOPSIS\fR
-.
-.IP
-puppet generate types [\-\-format \fIformat\fR] [\-\-force]
-.
-.IP
-\fBDESCRIPTION\fR
-.
-.IP
-Generates definitions for custom resource types using Puppet code\.
-.
-.IP
-Types defined in Puppet code can be used to isolate custom type definitions between different environments\.
-.
-.IP
-\fBOPTIONS\fR \fI\-\-force\fR \- Forces the generation of output files (skips up\-to\-date checks)\.
-.
-.IP
-\fI\-\-format <format\fR> \- The generation output format to use\. Supported formats: pcore\.
-.
-.SH "EXAMPLES"
-\fBtypes\fR
-.
-.P
-Generate Puppet type definitions for all custom resource types in the current environment:
-.
-.IP "" 4
-.
-.nf
-
-$ puppet generate types
-.
-.fi
-.
-.IP "" 0
-.
-.P
-Generate Puppet type definitions for all custom resource types in the specified environment:
-.
-.IP "" 4
-.
-.nf
-
-$ puppet generate types \-\-environment development
-.
-.fi
-.
-.IP "" 0
-.
-.SH "COPYRIGHT AND LICENSE"
-Copyright 2016 by Puppet Inc\. Apache 2 license; see COPYING

data/man/man8/puppet-lookup.8

@@ -1,87 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "PUPPET\-LOOKUP" "8" "May 2018" "Puppet, Inc." "Puppet manual"
-.
-.SH "NAME"
-\fBpuppet\-lookup\fR \- Data in modules lookup function
-.
-.SH "SYNOPSIS"
-The lookup command is used for debugging and testing a given data configuration\. For a given data key, lookup will produce either a value or an explanation of how that value was obtained on the standard output stream with the specified rendering format\. Lookup is designed to be run on a puppet master or a node in a masterless setup\.
-.
-.SH "USAGE"
-puppet lookup [\-\-help] [\-\-type \fITYPESTRING\fR] [\-\-merge unique|hash|deep] [\-\-knock\-out\-prefix \fIPREFIX\-STRING\fR] [\-\-sort\-merged\-arrays] [\-\-merge\-hash\-arrays] [\-\-explain] [\-\-default \fIVALUE\fR] [\-\-node \fINODE\-NAME\fR] [\-\-facts \fIFILE\fR] [\-\-compile] [\-\-render\-as s|json|yaml|binary|msgpack] \fIkeys\fR
-.
-.SH "DESCRIPTION"
-The lookup command is a CLI interface for the puppet lookup function\. When given one or more keys, the lookup command will return the first value found when run from the puppet master or a masterless node\.
-.
-.P
-When an explanation has not been requested and lookup is simply looking up a value, the application will exit with 0 if a value was found and 1 otherwise\. When an explanation is requested, lookup will always exit with 0 unless there is a major error\.
-.
-.P
-The other options are as passed into the lookup function, and the effect they have on the lookup is described in more detail in the header for the lookup function:
-.
-.P
-http://links\.puppetlabs\.com/lookup\-docs
-.
-.SH "OPTIONS"
-These options and their effects are described in more detail in the puppet lookup function linked to above\.
-.
-.IP "\(bu" 4
-\-\-help: Print this help message\.
-.
-.IP "\(bu" 4
-\-\-type \fITYPESTRING\fR: Assert that the value has the specified type\.
-.
-.IP "\(bu" 4
-\-\-merge unique|hash|deep: Specify the merge strategy\. \'hash\' performs a simple hash\-merge by overwriting keys of lower lookup priority\. \'unique\' appends everything to an array containing no nested arrays and where all duplicates have been removed\. \'deep\' Performs a deep merge on values of Array and Hash type\. There are additional option flags that can be used with \'deep\'\.
-.
-.IP "\(bu" 4
-\-\-knock\-out\-prefix \fIPREFIX\-STRING\fR Can be used with the \'deep\' merge strategy\. Specify string value to signify prefix which deletes elements from existing element\.
-.
-.IP "\(bu" 4
-\-\-sort\-merged\-arrays Can be used with the \'deep\' merge strategy\. When this flag is used all merged arrays will be sorted\.
-.
-.IP "\(bu" 4
-\-\-merge\-hash\-arrays Can be used with the \'deep\' merge strategy\. When this flag is used arrays and hashes will be merged\.
-.
-.IP "\(bu" 4
-\-\-explain Print an explanation for the details of how the lookup performed rather than the value returned for the key\. The explanation will describe how the result was obtained or why lookup failed to obtain the result\.
-.
-.IP "\(bu" 4
-\-\-explain\-options Explain if a lookup_options hash will be used and how it was assembled when performing a lookup\.
-.
-.IP "\(bu" 4
-\-\-default \fIVALUE\fR A value produced if no value was found in the lookup\.
-.
-.IP "\(bu" 4
-\-\-node \fINODE\-NAME\fR Specify node which defines the scope in which the lookup will be performed\. If a node is not given, lookup will default to the machine from which the lookup is being run (which should be the master)\.
-.
-.IP "\(bu" 4
-\-\-facts \fIFILE\fR Specify a \.json, or \.yaml file holding key => value mappings that will override the facts for the current node\. Any facts not specified by the user will maintain their original value\.
-.
-.IP "\(bu" 4
-\-\-compile Perform a full catalog compilation prior to the lookup\. This is meaningful when the catalog changes global variables that are referenced in interpolated values\. No catalog compilation takes place unless this flag is given\.
-.
-.IP "\(bu" 4
-\-\-render\-as s|json|yaml|binary|msgpack Determines how the results will be rendered to the standard output where s means plain text\. The default when lookup is producing a value is yaml and the default when producing an explanation is s\.
-.
-.IP "" 0
-.
-.SH "EXAMPLE"
-If you wanted to lookup \'key_name\' within the scope of the master, you would call lookup like this: $ puppet lookup key_name
-.
-.P
-If you wanted to lookup \'key_name\' within the scope of the agent\.local node, you would call lookup like this: $ puppet lookup \-\-node agent\.local key_name
-.
-.P
-If you wanted to get the first value found for \'key_name_one\' and \'key_name_two\' within the scope of the agent\.local node while merging values and knocking out the prefix \'foo\' while merging, you would call lookup like this: $ puppet lookup \-\-node agent\.local \-\-merge deep \-\-knock\-out\-prefix foo key_name_one key_name_two
-.
-.P
-If you wanted to lookup \'key_name\' within the scope of the agent\.local node, and return a default value of \'bar\' if nothing was found, you would call lookup like this: $ puppet lookup \-\-node agent\.local \-\-default bar key_name
-.
-.P
-If you wanted to see an explanation of how the value for \'key_name\' would be obtained in the context of the agent\.local node, you would call lookup like this: $ puppet lookup \-\-node agent\.local \-\-explain key_name
-.
-.SH "COPYRIGHT"
-Copyright (c) 2015 Puppet Inc\., LLC Licensed under the Apache 2\.0 License