-
Notifications
You must be signed in to change notification settings - Fork 21
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
template vars are missing scope #11
Comments
Thanks for the report @ThomasLohner. Just fixed puppet 4 support in commits f1b2bdc, a0c9958 and bebeea4 |
I meant puppet 4 / future parser / all deprecations-as-errors they use to introduce in minor versions (!) |
For the record, the change introduced in f1b2bdc breaks the module for puppet 3.8 in this way: https://tickets.puppetlabs.com/browse/PUP-4328 (last 5-6 comments). @ThomasLohner are you experiencing the same? |
It happens when for example you don't give a value to |
I had to disable system checks with Despite of this everything else works just fine on pupet 3.8.3. with future parser. Let me know if i can help somehow. |
I'm using this module with a puppet master 3.8.6 and i get lots of these errors:
This template is called by various defines which don't have a local variable called
alerts
, yet in the template you try to access@alterts
. Wouldn't the correct way bescope['monit::alerts']
?The same issue happens in /etc/monit/monitrc:
In the template it says
include <%= @conf_dir %>/*
and it's called from monit::config but there is no local paramconf_dir
in this class. Changing the template toinclude <%= scope['monit::conf_dir'] %>/*
fixes this problem.The text was updated successfully, but these errors were encountered: