On 07/14/2014 05:07 PM, Henrik Lindberg 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
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
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
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.
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
El 13/07/2014 18:32, Henrik Lindberg henrik.lindb...@cloudsmith.com
escribió:
On 2014-13-07 14:57, Felix Frank wrote:
On 07/13/2014 03:36 AM,
On 2014-11-07 16:38, Chris Cowley wrote:
OK, so what it the recommended way to do this? Somehow it is not
something I have come up against before, I have the impression that it
is a lot harder than simply:
if $variable {
do stuff
}
In version before Puppet 4.0.0 the values as boolean map
OK, so what it the recommended way to do this? Somehow it is not something
I have come up against before, I have the impression that it is a lot
harder than simply:
if $variable {
do stuff
}
I've had a look through stdlib and it does not seem to have anything that
helps here (if that is the
