| Age | Commit message (Collapse) | Author |
|---|
|
The `type()` function will cease to work on the new parser because 'type'
is a reserved keyword. The `type3x()` function may be used to continue
similar functionality, but will be deprecated in favor of the built-in
typing system.
The `type_of()` function has been included to introspect types in the
new parser.
|
|
|
|
|
|
Merge 4.5.x into master
|
|
These specs are pretty much the same as the originals, but now check that the output has the correct replacement for file location
|
|
poikilotherm/feature/master/validate_absolute_path_allow_arrays
Allow array of pathes in validate_absolute_path
|
|
Basename implementation
|
|
Based on dirname code. Includes RSpec tests and docs.
|
|
The `match` attribute was validated to match `line`, except that in many
cases (even the example given in the docs) a user would want to match a
line entirely different from the new line.
See comments on the original commit
https://github.com/puppetlabs/puppetlabs-stdlib/commit/a06c0d8115892a74666676b50d4282df9850a119
and ask
https://ask.puppetlabs.com/question/14366/file_line-resource-match-problems/
for further examples of confusion.
|
|
|
|
Also add extra test for just 1 argument
|
|
Acceptance test to take multiple arrays for concatenation
|
|
`concat` should be able to concat arrays and primitives
|
|
`concat` can now take multiple arguments
|
|
|
|
(MODULES-1329) Allow member to look for array
|
|
Make the range function work with integers
|
|
Currently, the member function allows one to only find if a variable
is part of an array. Sometimes it is useful to find if an array is part
of a bigger array for validation purpose.
|
|
|
|
This is needed for the future parser which actually treats numbers as
numbers and strings as strings. With this patch you can use range(1,5)
instead of having to quote them like range('1','5').
|
|
Update to fix ensure_resource as well
|
|
It should NOT run if the future parser is enabled
|
|
|
|
4.3.x
|
|
Added correct converstions for PB and EB.
|
|
MODULES-1413 Add ability for member to take numeric objects
|
|
|
|
Conflicts:
spec/acceptance/ensure_packages_spec.rb
spec/acceptance/ensure_resource_spec.rb
|
|
Conflicts:
spec/acceptance/ensure_packages_spec.rb
spec/acceptance/ensure_resource_spec.rb
|
|
|
|
3.7, previous version throw different exception. Wrapping in generic Exception catch all
|
|
|
|
which was not relavent to the host we were modifying
|
|
ruby and gem are not on the install path
|
|
|
|
that it was dealing with a string
|
|
* We were converting Exabytes to bytes as Petabytes.
* Updated tests to cover ever unit.
* Added note that we're going by the old, inaccurate definitions of
Kilobytes, Megabytes, etc, in that we treat them as powers of 2.
|
|
We need to use
unless value.is_a?(String) || value.is_a?(Array)
rather than
klass = value.class
unless [String, Array].include?(klass)
because the klass version enforces type checking which is too strict, and does
not allow us to accept objects wich have extended String (or Array).
For example, generate() function now returns Puppet::Util::Execution::ProcessOutput
which is just a very simple extension of String. While this in it's self was
not intentional (PUP-2306) it is not unreasonable to cope with objects which
extend Strings
|
|
simplecov 0.9 dropped ruby 1.8 support, and stdlib is one of the oddball
modules that uses it. So we could probably just remove it and be okay.
(cherry picked from commit a7c129b22d91fc723a8176c066a3eb96b03a2f56)
|
|
|
|
simplecov 0.9 dropped ruby 1.8 support, and stdlib is one of the oddball
modules that uses it. So we could probably just remove it and be okay.
|
|
|
|
It was discovered that the concat array modifies the arrays passed to it
as an argument as a side effect. This test will ensure that doesn't
happen again.
|
|
These functions take advantage of IP fact information and AIX does not
appear to support dynamic interface detection in facter.
|
|
|
|
|
|
|
|
|
|
|
|
|
