Issue #17350 has been updated by K J.
I have also encountered a similar issue.
The same error occurs when passing extra parameters to a resource that does not
accept them.
My hiera lookup was something like this:
website:
babies:
domain: babies.com
path: babies.com/path
where the defined type was
define babies($domain) {
}
And the error message was
Error: Invalid parameter path on node bar
Which was pretty hard to track down until I started checking out previous
versions of my puppet manifests till I found what made the change.
----------------------------------------
Feature #17350: improve invalid parameter error message from create resources
https://projects.puppetlabs.com/issues/17350#change-98849
* Author: Luke Bigum
* Status: Accepted
* Priority: Normal
* Assignee:
* Category:
* Target version:
* Affected Puppet version: 3.0.0
* Keywords: error message, usability
* Branch:
----------------------------------------
The error message from create_resources() when an invalid parameter is given is
a little difficult to understand.
For example if I have some Hiera data like this (where the 'enable' parameter
is mis-spelt as 'enabled'):
service:
puppet:
enabled: true
Then it would be more helpful if the error message looked something like this:
Invalid parameter "enabled" for resource type 'service' via
create_resources() on node foo
Instead of what it does now:
Invalid parameter enabled on node 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 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.
