Issue #22366 has been updated by Henrik Lindberg. Target version set to 3.5.0
This will be fixed in 3.5 (fix is already in future evaluator branch). The problem was not lack of validation, but a mistake in the model factory when creating the model object for Collection (it assumed it was given the string representing a qualified name instead of an already built expression - the reason it worked was because there was a check that if it got a pre-built QualifiedReference, then it skipped the creation. Output is now: Error: Could not parse for environment production: Illegal expression. A Literal Integer is unacceptable as type name in a Virtual Query at line 1:1 For the given scenario. ---------------------------------------- Bug #22366: The future parser validator doesn't catch using bad resource types in collection queries https://projects.puppetlabs.com/issues/22366#change-100141 * Author: Erik Dalén * Status: Accepted * Priority: Normal * Assignee: Henrik Lindberg * Category: parser * Target version: 3.5.0 * Affected Puppet version: 3.2.4 * Keywords: * Branch: ---------------------------------------- For example: puppet apply --parser=future -e '1<||>' Error: Resource type #<puppet::pops::model::literalnumber:0x007f822724c1c8> doesn't exist on node dalen -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
