One more, mostly just a 'wouldn't it be nice if this were clearly handled?'
Having a comma at the end of an assignment like the below appears to cause
confusion; mostly at this point my gripe is that the error line is reported
as the enclosing class/define/whatever instead of at the line with the
errant comma.
puppet parser validate --parser=future init.pp
Error: Could not parse for environment production: This Array Expression is
not productive. A Host Class Definition can not end with a non productive
construct at init.pp:1:1
class a {
$foo = "bar",
$banana = "apple"
}
On Monday, September 22, 2014 11:48:20 AM UTC-7, Tristan Smith wrote:
>
> So, new behavior that I'm not sure is intentional. File['blah'] works
> fine, File ['blah'] is now illegal - the additional whitespace causes the
> below stupendously readable error on puppet parser validate.
>
> Error: Could not parse for environment production: Expression is not valid
> as a resource, resource-default, or resource-override at (slice ()
> 'file'):(slice () 'line'):(slice ([] (cat '' (str $myvar) '')) 'pos')
>
> Is this a known bug I've failed to find on the ticket system, or intended
> behavior I've just missed in the notes? If not, I'll go chase it as a bug.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/27b39605-a929-4271-8a4b-b693337b7207%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
