| Age | Commit message (Collapse) | Author |
|---|
|
(MODULES-4097) Sync travis.yml
|
|
Release Prep for 4.15.0
|
|
|
|
|
|
|
|
Release mergeback - second attempt
|
|
* Release prep for 4.14.0
|
|
Addition of compat hash type for deprecation
|
|
|
|
|
|
add ubuntu xenial to metadata
|
|
|
|
Add puppet_server fact to return agent's server
|
|
Change - Update str2bool documentation
|
|
Updated documentation for this function to be consistent with
the function itself.
|
|
Add pry() function from hunner-pry
|
|
(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.
|
|
|
|
Release prep for 4.14.0
|
|
The previous release prep accidentally had 4.13.2 instead of 4.14.0 as is appropriate with releases with features. This is a PR to rectify that. No 4.13.2 release or tag will be made. The 4.14.0 release will go ahead instead.
|
|
Release prep for 4.13.2
|
|
|
|
(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
|
|
|
|
It is frequently useful to configure an agent to retrieve a resource
from it's configured master, or make further configuration adjustments
to itself based on what server it's using. Similar to the rationale for
stdlib providing a puppet_vardir fact, this commit adds a puppet_server
fact.
Note that the closest equivalent available today is $settings::server,
which returns only the MASTER's configured server, not the AGENT's. This
makes $settings::server unreliable, and not useful in a multi-master
deployment or a deployment involving a load balancer.
|
|
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.
|
