Issue #2896 has been updated by Daniel Pittman. Subject changed from --parseonly does not check resource parameters to `puppet parser validate` does not check resource parameters Description updated
The specific functionality, `--parseonly`, has been deprecated in favour of `puppet parser validate`, but the underlying issue remains. The actual challenge is that we really need almost an entire parser run to achieve the second half (defined types), and for the user to supply *all* the data the compiler would have. Just doing parameter checking for known types would almost be easy, except that same issue applies when custom types and providers come on the scene. ---------------------------------------- Feature #2896: `puppet parser validate` does not check resource parameters https://projects.puppetlabs.com/issues/2896 Author: Dan Bode Status: Accepted Priority: Normal Assignee: Category: parser Target version: 2.7.x Affected Puppet version: 0.25.1 Keywords: Branch: #>puppet --parseonly does not show an error when parsing: file{'name': bad_owner => 'invalid'} This should also work for resource definitions. my_def($param_a='_UNSET_') {} my_def{ 'my_def_1': pram_a => 'foo'; } -- 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.
