Issue #2896 has been updated by Nigel Kersten. Assignee set to eric sorenson
Josh Cooper wrote: > Going through the backlog. As of 2.7.18, `puppet parser validate` does not > validate parameters. The `paramcheck` option was removed in > <https://github.com/puppetlabs/puppet/commit/4709e9b> over two and a half > years ago. Given that `puppet apply --noop` does validate the type, provider, > parameters, etc, is there any reason to keep this issue open? Yes. noop still exports resources, updates facts in the inventory service, and basically has a whole bunch of implicit side-effects that mean that it's unsuitable for a pre-commit hook in your version control system. ---------------------------------------- Feature #2896: `puppet parser validate` does not check resource parameters https://projects.puppetlabs.com/issues/2896#change-67615 Author: Dan Bode Status: Accepted Priority: Normal Assignee: eric sorenson 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.
