Issue #4473 has been updated by Markus Roberts. Status changed from Unreviewed to Needs design decision Affected version deleted (2.6.1rc1)
"Fixing" this ticket could potentially cause wide spread breakage; even if it's accepted it shouldn't be in a point release. ---------------------------------------- Bug #4473: Parent class name is resolved within namespace of class being defined http://projects.puppetlabs.com/issues/4473 Author: Paul Berry Status: Needs design decision Priority: Normal Assigned to: Category: Target version: Affected version: Keywords: Branch: This issue came up in discussion with Jesse and Markus a few days ago and needs a design decision. It's a nonstandard behavior of Puppet that is potentially confusing and I suspect rarely used. The following is valid Puppet code and produces no error: <pre> class foo::bar { notify {"foo::bar": } } class foo inherits bar { notify {"bar": } } include foo </pre> I would expect the error: <pre> Could not find parent resource type 'bar' of type hostclass in production at .../init.pp:4 on node ... </pre> The issue is: when defining a class, should Puppet look inside that class's namespace when resolving the name of the parent class? In all programming languages I'm aware of, the answer would be no. However, the answer in Puppet has been "yes" since at least as far back as 0.25.5. So there is a danger that some customers are depending on this nonstandard behavior. -- 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.
