Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make compatible with strict variables. #66

Merged
merged 1 commit into from
Mar 1, 2016

Conversation

BobVincentatNCRdotcom
Copy link

Puppet 4 with strict variables aborts when referencing unset variables. Note that "unset" is not the same as "explicitly assigned an undef value".

@BobVincentatNCRdotcom
Copy link
Author

I have filed a bug report with Puppet including test code demonstrating that unset metaparameters are not assigned default values: https://tickets.puppetlabs.com/browse/PUP-5603

Update: The metaparameter bug was fixed in Puppet 4.3.0; see next comment.

@robbat2
Copy link

robbat2 commented Dec 13, 2015

+1 for merging. Then close #64 and #49

@BobVincentatNCRdotcom
Copy link
Author

Looks like the $schedule parameter workaround is only needed for puppet versions 4.0.0 - 4.2.3 inclusive. Puppet 4.3.0 fixes the bug. The $http_proxy and $https_proxy code is still necessary, unless you prefer the workaround suggested in #68

carlossg added a commit that referenced this pull request Mar 1, 2016
Make compatible with strict variables.
@carlossg carlossg merged commit 3ac0de8 into voxpupuli:master Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants