bolt 0.19.1 → 0.20.0

data/vendored/puppet/lib/puppet/parser/functions/fqdn_rand.rb

@@ -1,36 +0,0 @@
-require 'digest/md5'
-require 'digest/sha2'
-
-Puppet::Parser::Functions::newfunction(:fqdn_rand, :arity => -2, :type => :rvalue, :doc =>
-  "Usage: `fqdn_rand(MAX, [SEED])`. MAX is required and must be a positive
-  integer; SEED is optional and may be any number or string.
-
-  Generates a random Integer number greater than or equal to 0 and less than MAX,
-  combining the `$fqdn` fact and the value of SEED for repeatable randomness.
-  (That is, each node will get a different random number from this function, but
-  a given node's result will be the same every time unless its hostname changes.)
-
-  This function is usually used for spacing out runs of resource-intensive cron
-  tasks that run on many nodes, which could cause a thundering herd or degrade
-  other services if they all fire at once. Adding a SEED can be useful when you
-  have more than one such task and need several unrelated random numbers per
-  node. (For example, `fqdn_rand(30)`, `fqdn_rand(30, 'expensive job 1')`, and
-  `fqdn_rand(30, 'expensive job 2')` will produce totally different numbers.)") do |args|
-    max = args.shift.to_i
- 
-    # Puppet 5.4's fqdn_rand function produces a different value than earlier versions
-    # for the same set of inputs.
-    # This causes problems because the values are often written into service configuration files.
-    # When they change, services get notified and restart.
-
-    # Restoring previous fqdn_rand behavior of calculating its seed value using MD5
-    # when running on a non-FIPS enabled platform and only using SHA256 on FIPS enabled
-    # platforms.
-    if Puppet::Util::Platform.fips_enabled?
-      seed = Digest::SHA256.hexdigest([self['::fqdn'],max,args].join(':')).hex
-    else
-      seed = Digest::MD5.hexdigest([self['::fqdn'],max,args].join(':')).hex
-    end
-
-    Puppet::Util.deterministic_rand_int(seed,max)
-end

data/vendored/puppet/lib/puppet/parser/functions/generate.rb

@@ -1,36 +0,0 @@
-# Runs an external command and returns the results
-Puppet::Parser::Functions::newfunction(:generate, :arity => -2, :type => :rvalue,
-    :doc => "Calls an external command on the Puppet master and returns
-    the results of the command.  Any arguments are passed to the external command as
-    arguments.  If the generator does not exit with return code of 0,
-    the generator is considered to have failed and a parse error is
-    thrown.  Generators can only have file separators, alphanumerics, dashes,
-    and periods in them.  This function will attempt to protect you from
-    malicious generator calls (e.g., those with '..' in them), but it can
-    never be entirely safe.  No subshell is used to execute
-    generators, so all shell metacharacters are passed directly to
-    the generator.") do |args|
-
-      #TRANSLATORS "fully qualified" refers to a fully qualified file system path
-      raise Puppet::ParseError, _("Generators must be fully qualified") unless Puppet::Util.absolute_path?(args[0])
-
-      if Puppet.features.microsoft_windows?
-        valid = args[0] =~ /^[a-z]:(?:[\/\\][-.~\w]+)+$/i
-      else
-        valid = args[0] =~ /^[-\/\w.+]+$/
-      end
-
-      unless valid
-        raise Puppet::ParseError, _("Generators can only contain alphanumerics, file separators, and dashes")
-      end
-
-      if args[0] =~ /\.\./
-        raise Puppet::ParseError, _("Can not use generators with '..' in them.")
-      end
-
-      begin
-        Dir.chdir(File.dirname(args[0])) { Puppet::Util::Execution.execute(args).to_str }
-      rescue Puppet::ExecutionFailure => detail
-        raise Puppet::ParseError, _("Failed to execute generator %{generator}: %{detail}") % { generator: args[0], detail: detail }, detail.backtrace
-      end
-end

data/vendored/puppet/lib/puppet/parser/functions/hiera.rb

@@ -1,103 +0,0 @@
-require 'hiera_puppet'
-
-module Puppet::Parser::Functions
-  newfunction(
-    :hiera,
-    :type => :rvalue,
-    :arity => -2,
-    :doc => <<DOC
-Performs a standard priority lookup of the hierarchy and returns the most specific value
-for a given key. The returned value can be any type of data.
-
-The function takes up to three arguments, in this order:
-
-1. A string key that Hiera searches for in the hierarchy. **Required**.
-2. An optional default value to return if Hiera doesn't find anything matching the key.
-    * If this argument isn't provided and this function results in a lookup failure, Puppet
-    fails with a compilation error.
-3. The optional name of an arbitrary
-[hierarchy level](https://docs.puppetlabs.com/hiera/latest/hierarchy.html) to insert at the
-top of the hierarchy. This lets you temporarily modify the hierarchy for a single lookup.
-    * If Hiera doesn't find a matching key in the overriding hierarchy level, it continues
-    searching the rest of the hierarchy.
-
-The `hiera` function does **not** find all matches throughout a hierarchy, instead
-returining the first specific value starting at the top of the hierarchy. To search
-throughout a hierarchy, use the `hiera_array` or `hiera_hash` functions.
-
-**Example**: Using `hiera`
-
-~~~ yaml
-# Assuming hiera.yaml
-# :hierarchy:
-#   - web01.example.com
-#   - common
-
-# Assuming web01.example.com.yaml:
-# users:
-#   - "Amy Barry"
-#   - "Carrie Douglas"
-
-# Assuming common.yaml:
-users:
-  admins:
-    - "Edith Franklin"
-    - "Ginny Hamilton"
-  regular:
-    - "Iris Jackson"
-    - "Kelly Lambert"
-~~~
-
-~~~ puppet
-# Assuming we are not web01.example.com:
-
-$users = hiera('users', undef)
-
-# $users contains {admins  => ["Edith Franklin", "Ginny Hamilton"],
-#                  regular => ["Iris Jackson", "Kelly Lambert"]}
-~~~
-
-You can optionally generate the default value with a
-[lambda](https://docs.puppetlabs.com/puppet/latest/reference/lang_lambdas.html) that
-takes one parameter.
-
-**Example**: Using `hiera` with a lambda
-
-~~~ puppet
-# Assuming the same Hiera data as the previous example:
-
-$users = hiera('users') | $key | { "Key \'${key}\' not found" }
-
-# $users contains {admins  => ["Edith Franklin", "Ginny Hamilton"],
-#                  regular => ["Iris Jackson", "Kelly Lambert"]}
-# If hiera couldn't match its key, it would return the lambda result,
-# "Key 'users' not found".
-~~~
-
-The returned value's data type depends on the types of the results. In the example
-above, Hiera matches the 'users' key and returns it as a hash.
-
-The `hiera` function is deprecated in favor of using `lookup` and will be removed in 6.0.0.
-See  https://docs.puppet.com/puppet/#{Puppet.minor_version}/reference/deprecated_language.html.
-Replace the calls as follows:
-
-| from  | to |
-| ----  | ---|
-| hiera($key) | lookup($key) |
-| hiera($key, $default) | lookup($key, { 'default_value' => $default }) |
-| hiera($key, $default, $level) | override level not supported |
-
-Note that calls using the 'override level' option are not directly supported by 'lookup' and the produced
-result must be post processed to get exactly the same result, for example using simple hash/array `+` or
-with calls to stdlib's `deep_merge` function depending on kind of hiera call and setting of merge in hiera.yaml.
-
-See
-[the documentation](https://docs.puppetlabs.com/hiera/latest/puppet.html#hiera-lookup-functions)
-for more information about Hiera lookup functions.
-
-- Since 4.0.0
-DOC
-  ) do |*args|
-    Error.is4x('hiera')
-  end
-end

data/vendored/puppet/lib/puppet/parser/functions/hiera_array.rb

@@ -1,92 +0,0 @@
-require 'hiera_puppet'
-
-module Puppet::Parser::Functions
-  newfunction(
-    :hiera_array,
-    :type => :rvalue,
-    :arity => -2,
-    :doc => <<-DOC
-Finds all matches of a key throughout the hierarchy and returns them as a single flattened
-array of unique values. If any of the matched values are arrays, they're flattened and
-included in the results. This is called an
-[array merge lookup](https://docs.puppetlabs.com/hiera/latest/lookup_types.html#array-merge).
-
-The `hiera_array` function takes up to three arguments, in this order:
-
-1. A string key that Hiera searches for in the hierarchy. **Required**.
-2. An optional default value to return if Hiera doesn't find anything matching the key.
-    * If this argument isn't provided and this function results in a lookup failure, Puppet
-    fails with a compilation error.
-3. The optional name of an arbitrary
-[hierarchy level](https://docs.puppetlabs.com/hiera/latest/hierarchy.html) to insert at the
-top of the hierarchy. This lets you temporarily modify the hierarchy for a single lookup.
-    * If Hiera doesn't find a matching key in the overriding hierarchy level, it continues
-    searching the rest of the hierarchy.
-
-**Example**: Using `hiera_array`
-
-~~~ yaml
-# Assuming hiera.yaml
-# :hierarchy:
-#   - web01.example.com
-#   - common
-
-# Assuming common.yaml:
-# users:
-#   - 'cdouglas = regular'
-#   - 'efranklin = regular'
-
-# Assuming web01.example.com.yaml:
-# users: 'abarry = admin'
-~~~
-
-~~~ puppet
-$allusers = hiera_array('users', undef)
-
-# $allusers contains ["cdouglas = regular", "efranklin = regular", "abarry = admin"].
-~~~
-
-You can optionally generate the default value with a
-[lambda](https://docs.puppetlabs.com/puppet/latest/reference/lang_lambdas.html) that
-takes one parameter.
-
-**Example**: Using `hiera_array` with a lambda
-
-~~~ puppet
-# Assuming the same Hiera data as the previous example:
-
-$allusers = hiera_array('users') | $key | { "Key \'${key}\' not found" }
-
-# $allusers contains ["cdouglas = regular", "efranklin = regular", "abarry = admin"].
-# If hiera_array couldn't match its key, it would return the lambda result,
-# "Key 'users' not found".
-~~~
-
-`hiera_array` expects that all values returned will be strings or arrays. If any matched
-value is a hash, Puppet raises a type mismatch error.
-
-`hiera_array` is deprecated in favor of using `lookup` and will be removed in 6.0.0.
-See  https://docs.puppet.com/puppet/#{Puppet.minor_version}/reference/deprecated_language.html.
-Replace the calls as follows:
-
-| from  | to |
-| ----  | ---|
-| hiera_array($key) | lookup($key, { 'merge' => 'unique' }) |
-| hiera_array($key, $default) | lookup($key, { 'default_value' => $default, 'merge' => 'unique' }) |
-| hiera_array($key, $default, $level) | override level not supported |
-
-Note that calls using the 'override level' option are not directly supported by 'lookup' and the produced
-result must be post processed to get exactly the same result, for example using simple hash/array `+` or
-with calls to stdlib's `deep_merge` function depending on kind of hiera call and setting of merge in hiera.yaml.
-
-See
-[the documentation](https://docs.puppetlabs.com/hiera/latest/puppet.html#hiera-lookup-functions)
-for more information about Hiera lookup functions.
-
-- Since 4.0.0
-DOC
-) do |*args|
-    Error.is4x('hiera_array')
-  end
-end
-

data/vendored/puppet/lib/puppet/parser/functions/hiera_hash.rb

@@ -1,102 +0,0 @@
-require 'hiera_puppet'
-
-module Puppet::Parser::Functions
-  newfunction(
-    :hiera_hash,
-    :type => :rvalue,
-    :arity => -2,
-    :doc => <<-DOC
-Finds all matches of a key throughout the hierarchy and returns them in a merged hash.
-If any of the matched hashes share keys, the final hash uses the value from the
-highest priority match. This is called a
-[hash merge lookup](https://docs.puppetlabs.com/hiera/latest/lookup_types.html#hash-merge).
-
-The merge strategy is determined by Hiera's
-[`:merge_behavior`](https://docs.puppetlabs.com/hiera/latest/configuring.html#mergebehavior)
-setting.
-
-The `hiera_hash` function takes up to three arguments, in this order:
-
-1. A string key that Hiera searches for in the hierarchy. **Required**.
-2. An optional default value to return if Hiera doesn't find anything matching the key.
-    * If this argument isn't provided and this function results in a lookup failure, Puppet
-    fails with a compilation error.
-3. The optional name of an arbitrary
-[hierarchy level](https://docs.puppetlabs.com/hiera/latest/hierarchy.html) to insert at the
-top of the hierarchy. This lets you temporarily modify the hierarchy for a single lookup.
-    * If Hiera doesn't find a matching key in the overriding hierarchy level, it continues
-    searching the rest of the hierarchy.
-
-**Example**: Using `hiera_hash`
-
-~~~ yaml
-# Assuming hiera.yaml
-# :hierarchy:
-#   - web01.example.com
-#   - common
-
-# Assuming common.yaml:
-# users:
-#   regular:
-#     'cdouglas': 'Carrie Douglas'
-
-# Assuming web01.example.com.yaml:
-# users:
-#   administrators:
-#     'aberry': 'Amy Berry'
-~~~
-
-~~~ puppet
-# Assuming we are not web01.example.com:
-
-$allusers = hiera_hash('users', undef)
-
-# $allusers contains {regular => {"cdouglas" => "Carrie Douglas"},
-#                     administrators => {"aberry" => "Amy Berry"}}
-~~~
-
-You can optionally generate the default value with a
-[lambda](https://docs.puppetlabs.com/puppet/latest/reference/lang_lambdas.html) that
-takes one parameter.
-
-**Example**: Using `hiera_hash` with a lambda
-
-~~~ puppet
-# Assuming the same Hiera data as the previous example:
-
-$allusers = hiera_hash('users') | $key | { "Key \'${key}\' not found" }
-
-# $allusers contains {regular => {"cdouglas" => "Carrie Douglas"},
-#                     administrators => {"aberry" => "Amy Berry"}}
-# If hiera_hash couldn't match its key, it would return the lambda result,
-# "Key 'users' not found".
-~~~
-
-`hiera_hash` expects that all values returned will be hashes. If any of the values
-found in the data sources are strings or arrays, Puppet raises a type mismatch error.
-
-`hiera_hash` is deprecated in favor of using `lookup` and will be removed in 6.0.0.
-See  https://docs.puppet.com/puppet/#{Puppet.minor_version}/reference/deprecated_language.html.
-Replace the calls as follows:
-
-| from  | to |
-| ----  | ---|
-| hiera_hash($key) | lookup($key, { 'merge' => 'hash' }) |
-| hiera_hash($key, $default) | lookup($key, { 'default_value' => $default, 'merge' => 'hash' }) |
-| hiera_hash($key, $default, $level) | override level not supported |
-
-Note that calls using the 'override level' option are not directly supported by 'lookup' and the produced
-result must be post processed to get exactly the same result, for example using simple hash/array `+` or
-with calls to stdlib's `deep_merge` function depending on kind of hiera call and setting of merge in hiera.yaml.
-
-See
-[the documentation](https://docs.puppetlabs.com/hiera/latest/puppet.html#hiera-lookup-functions)
-for more information about Hiera lookup functions.
-
-- Since 4.0.0
-DOC
-  ) do |*args|
-    Error.is4x('hiera_hash')
-  end
-end
-

data/vendored/puppet/lib/puppet/parser/functions/hiera_include.rb

@@ -1,102 +0,0 @@
-require 'hiera_puppet'
-
-module Puppet::Parser::Functions
-  newfunction(
-    :hiera_include,
-    :arity => -2,
-    :doc => <<-DOC
-Assigns classes to a node using an
-[array merge lookup](https://docs.puppetlabs.com/hiera/latest/lookup_types.html#array-merge)
-that retrieves the value for a user-specified key from Hiera's data.
-
-The `hiera_include` function requires:
-
-- A string key name to use for classes.
-- A call to this function (i.e. `hiera_include('classes')`) in your environment's
-`sites.pp` manifest, outside of any node definitions and below any top-scope variables
-that Hiera uses in lookups.
-- `classes` keys in the appropriate Hiera data sources, with an array for each
-`classes` key and each value of the array containing the name of a class.
-
-The function takes up to three arguments, in this order:
-
-1. A string key that Hiera searches for in the hierarchy. **Required**.
-2. An optional default value to return if Hiera doesn't find anything matching the key.
-    * If this argument isn't provided and this function results in a lookup failure, Puppet
-    fails with a compilation error.
-3. The optional name of an arbitrary
-[hierarchy level](https://docs.puppetlabs.com/hiera/latest/hierarchy.html) to insert at the
-top of the hierarchy. This lets you temporarily modify the hierarchy for a single lookup.
-    * If Hiera doesn't find a matching key in the overriding hierarchy level, it continues
-    searching the rest of the hierarchy.
-
-The function uses an
-[array merge lookup](https://docs.puppetlabs.com/hiera/latest/lookup_types.html#array-merge)
-to retrieve the `classes` array, so every node gets every class from the hierarchy.
-
-**Example**: Using `hiera_include`
-
-~~~ yaml
-# Assuming hiera.yaml
-# :hierarchy:
-#   - web01.example.com
-#   - common
-
-# Assuming web01.example.com.yaml:
-# classes:
-#   - apache::mod::php
-
-# Assuming common.yaml:
-# classes:
-#   - apache
-~~~
-
-~~~ puppet
-# In site.pp, outside of any node definitions and below any top-scope variables:
-hiera_include('classes', undef)
-
-# Puppet assigns the apache and apache::mod::php classes to the web01.example.com node.
-~~~
-
-You can optionally generate the default value with a
-[lambda](https://docs.puppetlabs.com/puppet/latest/reference/lang_lambdas.html) that
-takes one parameter.
-
-**Example**: Using `hiera_include` with a lambda
-
-~~~ puppet
-# Assuming the same Hiera data as the previous example:
-
-# In site.pp, outside of any node definitions and below any top-scope variables:
-hiera_include('classes') | $key | {"Key \'${key}\' not found" }
-
-# Puppet assigns the apache and apache::mod::php classes to the web01.example.com node.
-# If hiera_include couldn't match its key, it would return the lambda result,
-# "Key 'classes' not found".
-~~~
-
-`hiera_include` is deprecated in favor of using a combination of `include`and `lookup` and will be
-removed in 6.0.0. See  https://docs.puppet.com/puppet/#{Puppet.minor_version}/reference/deprecated_language.html.
-Replace the calls as follows:
-
-| from  | to |
-| ----  | ---|
-| hiera_include($key) | include(lookup($key, { 'merge' => 'unique' })) |
-| hiera_include($key, $default) | include(lookup($key, { 'default_value' => $default, 'merge' => 'unique' })) |
-| hiera_include($key, $default, $level) | override level not supported |
-
-Note that calls using the 'override level' option are not directly supported by 'lookup' and the produced
-result must be post processed to get exactly the same result, for example using simple hash/array `+` or
-with calls to stdlib's `deep_merge` function depending on kind of hiera call and setting of merge in hiera.yaml.
-
-See [the documentation](http://links.puppet.com/hierainclude) for more information
-and a more detailed example of how `hiera_include` uses array merge lookups to classify
-nodes.
-
-- Since 4.0.0
-DOC
-  ) do |*args|
-    Error.is4x('hiera_include')
-  end
-end
-