Jira (PUP-2837) alter parser to throw an error on use of an undefined, unquoted, variable.

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: alter parser to throw an error on use of an undefined, unquoted, variable. In the 3x "future parser", undefined variables all have the value undef and this value renders as an empty string when interpolated. Since (IIRC 3.5.0) it is possible to turn on --strict_variables and get an error whenever an undefined variable (one that has never been initialized, not even to undef). The intent is to keep this as optional behavior also in Puppet 4.0 simply because changing this would cause breaking a lot of code. We are hoping to be able to enforce --strict_variables in Puppet 5.0. The mixed "undefined variables can be interpolated"-mode would just make everything even more confusing, and this is not something that we have considered implementing. We already have a ticket for "Make variables strict by default", so I am closing this as a duplicate. Add Comment   Puppet / PUP-2837 alter parser to throw an error on use of an undefined, unquoted, variable. Currently, the parser treats the following cases as equivalent: <pre> file {"/tmp/testfile":     content => $content } file {"/tmp/testfile":     content => "$content" } </pre> I think it would be beneficial to throw a compile error in the first case if $content is not defined, eg fail('Attempt to use unquoted, undefined variable $conte... 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.