Age | Commit message (Collapse) | Author |
|
(FM-5972) gettext and spec.opts
|
|
|
|
(MODULES-4188) Add UUID generation function
|
|
HAIL9000/issue/master/MODULES-3829_add_tests_for_ensure_resources
(MODULES-3829) Add tests for ensure_resources
|
|
Prior to this commit, if a hash was passed in as an
argument to the ensure_packages function a method of
hash duplication would be used that is not supported
with versions of ruby older than 2.0. In order to
ensure the method is compatible with older ruby versions,
switch to a different method of duplication.
Additionally add tests to prevent further regressions.
|
|
* Generates UUID based on a given FQDN string and the DNS namespace (6ba7b810-9dad-11d1-80b4-00c04fd430c8)
|
|
Prior to this commit, we didn't have tests for the ensure_resources
function (only for the ensure_resource function). This meant that
we weren't catching a bug in the ensure_resources function. In order
to prevent this in the future, add some tests which test the
specific functionality of ensure_resources.
|
|
(MODULES-3631) msync Gemfile for 1.9 frozen strings
|
|
|
|
Prior to this commit, users coming to the type_of function would not realize that the type function in puppet does the same thing and is preferred over type_of.
After this commit, we have a comment indicating the above.
|
|
(MODULES-3393) Deprecation - Use puppet stacktrace if available
|
|
|
|
Remove rvalue declaration from v3 deprecation() function
|
|
Without this, some uses of this function do not work in puppet3. e.g.
if $include_src != undef {
deprecation('apt $include_src', "please use \$include => { 'src' => ${include_src} } instead")
}
causes
Function 'deprecation' must be the value of a statement
on puppet 3.8.7.
|
|
A previous PR (#685) was raised on this issue, however once it was merged it was discovered that Puppet 3 with future parser enabled was calling the Puppet 4 version of the deprecation function. The Puppet stacktrace is not available until Puppet 4.6, so this was breaking existing setups. The solution was to check is the stacktrace was defined, and if it was to use it as part of the message output.
|
|
Fixing broken link to #validate_legacy docs
|
|
Revert "Call site output for deprecation warnings"
|
|
|
|
Call site output for deprecation warnings
|
|
|
|
|
|
MODULES-4008: clarify deprecation language
|
|
|
|
(MODULES-3704) Update gemfile template to be identical
|
|
|
|
Handle array values in join_keys_to_values function
|
|
Fix spec failures on puppet 4.8
|
|
These were caused by a change in the tested error message.
|
|
Addition of 4.6 and 4.7 travis cells
|
|
Remove leading spaces
|
|
(MODULES-3829) Use .dup to duplicate classes for modification.
|
|
This function otherwise fails during `puppet preview` on Puppet 3.8.X systems.
|
|
|
|
This corrects puppet-linting error.
|
|
(MODULES-3980) Fix ipv4 regex validator
|
|
This also updates all ipv4 tests to use the same test data for better
comparability. Closes #676, #679
Fix-Originally-By: Nate Potter <nathaniel.potter@intel.com>
|
|
This is to pin ruby version to parallel_tests
|
|
|
|
Fix incorrect environment variable name in README
|
|
The README references the environment variable `STDLIB_LOG_DEPRECATION`
while the code uses `STDLIB_LOG_DEPRECATIONS` (note the trailing S).
|
|
(MODULES-3969) Update getvar to work on ruby 1.8.7
|
|
|
|
|
|
(MODULES-3962) Rework v4 function shims to work on puppet 3.7 and 4.0.0
|
|
This is a workaround for PUP-4438 (fixed in https://github.com/puppetlabs/puppet/commit/e01c4dc924cd963ff6630008a5200fc6a2023b08, 4.1.0, 3.8.1).
It works by manually passing through the scope, instead of relying on the
InternalFunction class.
|
|
(MODULES-3961) emit more deprecation warnings
|
|
This now emits one deprecation warning for each function used (but not for each call-site). Prior to this, only a single deprecation warning would have been triggered, potentially misleading users.
Additionally this adds v4 deprecation stubs for the functions that were missed.
|
|
Mergeback
|
|
Release prep for 4.13.0
|
|
Apparently mocha 1.2.0 causes an endless hang
on spec/unit/facter/root_home_spec.rb. Forcing
an earlier version avoids this for now.
|