Make module behaviour consistent despite value of stringify_facts #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, it's possible that the comparison on the
$::has_compiler
fact may not return the intended result depending on the value ofstringify_facts
inpuppet.conf
.In Puppet 3, this value defaults to
true
which means all Facts when looked up are passed through#to_s
. This means that if the fact has the value offalse
, it will be considered true when evaluated.To illustrate this, consider the following:
If I remember correctly, even blank strings returned from Facter will evaluate to true when flattened.
Since there's already a dependancy on
puppetlabs-stdlib
, we can usestr2bool()
to make this backwards compatible. It's a recommended method from Puppet themselves during the upgrade process (source)