-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
Collectd version fact value #707
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that in this case it does make sense to return false.
Strange thing here is that our tests were green before this change, so they didn't detect this error. Conclusion: We don't have a test that proves that this change fixes anything / breaks nothing. In theory the puppetlabs_spec_helper enables STRICT_VARIABLES. It needs to be checked if this is actually the case, or if we need more tests here. |
@ctriegg cna you also please check the used email address in your commit? It isn't associated with your github account. |
@bastelfreak we ensure the fact is present in our tests:
|
I'm not sure this is the right fix. As per our own docs, we shouldn't be using top scope variables to access facts. I think changing init.pp line 37
to
would be better. |
Actually, I think this isn't just a style thing. This PR introduces a bug. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR breaks the minimum_version
parameter.
alexjfisher is right. just running tests, pushing it when they're finished |
@ctriegg I've already got #708 open (which includes a similar fix for |
@ctriegg Thank you for looking into this. |
fixes issue #700