Jira (PUP-1540) Puppet should support compilation failure if a variable is undefined

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Puppet should support compilation failure if a variable is undefined Does the option in Puppet 3.5.0 --strict_variables = true do what is wanted? It works for both --parser-future and regular parser. puppet apply -e 'notice $a' --strict_variables Error: Undefined variable "a" at line 1 on node kermit.example.local For 4x, the idea is to make this option default to true. Add Comment   Puppet / PUP-1540 Puppet should support compilation failure if a variable is undefined Currently, if a variable is undefined in puppet code, compilation succeeds, and the value is undef. E.g. {noformat} notify { $foo: } {noformat} results in {noformat} Notice: /Stage[main]//Notify[undef]/message: defined 'message' as 'undef' {noformat} Similarly, if you try to use an undefined variable inside a template, in interpolates to an ... 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.