On 2014-13-07 22:58, José Luis Ledesma wrote:
From my point of view is better a warning when a empty string is taken as a false, than some configuration applied erroneously once upgraded to 4.0
We encourage testing with 3.7 future parser. If it turns out to be a problem for many (breakage due to undef/'' change) we will see what we can do about it. We are not sure we can find and efficiently check all occurrences as it involves reporting all places where an undef was not turned into a string that is passed off to logic that may or may not compare it to a Boolean. (This is the very essence of the problem; not knowing if something is a defined string or not later in the evaluation).
I can also highly recommend using rspec-puppet and writing catalog unit tests to ensure that your catlogs do not regress (because of changes in Puppet, changes in modules you use, or indeed changes in your own modules).
Regards - henrik
El 13/07/2014 18:32, "Henrik Lindberg" <henrik.lindb...@cloudsmith.com <mailto:henrik.lindb...@cloudsmith.com>> escribió: On 2014-13-07 14:57, Felix Frank wrote: On 07/13/2014 03:36 AM, Henrik Lindberg wrote: "falsey": empty string, false, undef "truthy": everything else In Puppet 4.0.0 this will be: "falsey": false, undef "truthy": everything else Oops? Interesting. This will break O(50%) of my manifests. Good to know, seeing as there is likely no deprecation warning for "you are apparently using an empty string in boolean context", right? Yes, no deprecation issued as that would create an avalanche of deprecations. Best approach is to test with --parser future. - henrik -- Visit my Blog "Puppet on the Edge" http://puppet-on-the-edge.__blogspot.se/ <http://puppet-on-the-edge.blogspot.se/> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@__googlegroups.com <mailto:puppet-users%2bunsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-users/lpuca7%__249ap%241%40ger.gmane.org <https://groups.google.com/d/msgid/puppet-users/lpuca7%249ap%241%40ger.gmane.org>. For more options, visit https://groups.google.com/d/__optout <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com <mailto:puppet-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAF_B3dda_ij%2B8HCi%3DRMCv_e2gx-%2BMYraB7nPByddMZDpCL9Eyg%40mail.gmail.com <https://groups.google.com/d/msgid/puppet-users/CAF_B3dda_ij%2B8HCi%3DRMCv_e2gx-%2BMYraB7nPByddMZDpCL9Eyg%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout.
-- Visit my Blog "Puppet on the Edge" http://puppet-on-the-edge.blogspot.se/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/lq0ro8%245ou%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout.
