Issue #14109 has been updated by Daniel Pittman. Category set to error reporting Status changed from Unreviewed to Accepted Target version set to Telly
That is true - the failure may be triggered by the resource, but the root cause is associated with the override. We should, indeed, report the problem point as the override rather than the resource itself. ---------------------------------------- Bug #14109: Bad error message if you pass an invalid parameter to an override by collection block https://projects.puppetlabs.com/issues/14109#change-61068 Author: Joe McDonagh Status: Accepted Priority: Normal Assignee: Category: error reporting Target version: Telly Affected Puppet version: Keywords: Branch: Say I override by collection something called accounts::ssh_user with an invalid parameter like so: Accounts::Ssh_user <| tag == 'sometag' |> { ensire => $ensure } Notice the ensire typo. Puppet will say invalid parameter ensire and point at the file where the users are, versus where the override is. Can cause a lot of tail chasing. -- 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.
