Jira (PUP-2735) unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters This works as intended. Puppet 3x does not have a numeric type - all numbers are strings. When numeric data is passed it is (typically not transformed, but it may be in some situations). This is a source of great pain. In Puppet 4.0, there is a difference between numeric values and strings - this can be tested using the --parser future option. I would very much appreciate if you could try your scenario with --parser future turned on and report how that works. Add Comment   Puppet / PUP-2735 unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters I'm not sure, if this should be considered as an error. At least it should be stressed in the documentation: 0 (a digit) used as default value of a class parameter is converted into a string or character when the variable is interpreted in a template by Ruby. On the other hand, 0 entered as a value in an hiera-yaml file is interpreted as an integer va... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.