Jira (PUP-2552) Future parser breaks concat module

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: Future parser breaks concat module Nitzan Raz, thank you for the report. I think the behavior you are seeing is because you are specifying the fragment order like so: order => 001. Under the current parser 001 is actually treated as a bareword string, which means that it is equivalent to "001". However, the new parser is treating anything that is a numeric literal as a number, which causes 001 to be treated as the octal number 1. When the number is then interpolated into the string to construct the filename it is then stringified as the decimal representation of the number 1, which is simply 1. You can fix this in your manifests by specifying the value 001 as a string literal of "001". Add Comment   Puppet / PUP-2552 Future parser breaks concat module When enabling future parser by specifying {quote} parser = future {quote} in puppet.conf, leading zeroes are removed from integers, disrupting file order in concat. For example, with future parser, keepalived creates this fragment: {quote} 1_keepalived.conf_header {quote} and not: {quote} 001_keepalived.conf_header {quote} Creating bad orderin... 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.