Issue #4408 has been updated by Ben Marcotte.
Robert, that looks exactly like an issue that I submitted as bug #12567. That ticket has been accepted and is targeted to Telly, but I haven't seen any updates on it for roughly two months. I started watching this ticket since the fallout from that bug is undefined variables, and I most wholeheartedly agree there needs to be some type of mechanism to assert that variables with undefined values cause some type of warning or error, so issues like this can be caught more easily. ---------------------------------------- Feature #4408: A 'strict' variable mode should be added https://projects.puppetlabs.com/issues/4408#change-60701 Author: Stig Sandbeck Mathisen Status: Accepted Priority: Normal Assignee: Category: language Target version: Affected Puppet version: 0.25.1 Keywords: Branch: This is an issue reported in the Debian Bug Tracker at [[http://bugs.debian.org/563550]]. Excerpt: <blockquote> The puppet manifest language uses empty variables the same way then undefined ones. Many languages, for example perl and sql, have shown in the past that this behaviour produces hard to find errors all over the code. Example: lsb* are undefined if lsb-release is missing. A definition using this needs to explicitely check for the lack of a value. It would be obvious if it bails out on the variable access. This is also different from the behaviour of the templating language, erb bails out on undefined variables. </blockquote> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
