Jira (PUP-1349) improve error message when File[undef] occurs

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: improve error message when File[undef] occurs There are two issues outlined by this problem; the first is that the location of the failing parameter is not printed, and the second is that there is no indication that there is an invalid path vs the 'undef' parameter. It looks like the first issue was resolved in 38ef0c5564de8062a1fccbc0bf9331cee8f7b6de: Author: Dominic Cleal <dcl...@redhat.com> Date: Sun Mar 3 12:11:19 2013 +0000 (#19558) Add manifest file/line to parameter validation failures For consistency, provide manifest file and line number in the error message when a parameter fails to validate. This was fixed in 3.2.0. The second issue has a pull request filed at https://github.com/puppetlabs/puppet/pull/2245. Add Comment   Puppet / PUP-1349 improve error message when File[undef] occurs If you create a File resource from a variable that is not defined, the error message doesn't mention the position in the manifest nor the class name that the problematic resource occurs in. This makes it difficult to find out which File resource is broken.     $ echo 'file { $foo: ensure => present }' | puppet apply     Error: Failed to apply catalog:... 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/groups/opt_out.