Issue #10443 has been updated by Nigel Kersten. Status changed from Unreviewed to Accepted
I'm completely behind this in principle. We need a better sense of the ramifications though. ---------------------------------------- Feature #10443: resource_type should conform to module auto-loading rules https://projects.puppetlabs.com/issues/10443 Author: Dan Bode Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: given the following module path: <pre> # find * foo foo/manifests foo/manifests/bar.pp </pre> and the fact that the namespace of the class defined in bar.pp does not correlated to its file path (as per auto-loading rules) <pre> # cat foo/manifests/bar.pp class blah {} </pre> the following call to resource_type search should not return the class: <pre> puppet resource_type search '*' --modulepath /Users/danbode/test [{"name":"blah","line":1,"type":"hostclass","file":"/Users/danbode/test/foo/manifests/bar.pp"}] </pre> at the very least, it should indicate that it is not loadable (maybe as an attribute) to further illustrate the point: <pre> puppet apply --modulepath /Users/danbode/test -e 'include blah' Could not find class blah for danbodesmac.puppetlabs.lan at line 1 on node danbodesmac.puppetlabs.lan </pre> The argument against this could be that the class is loadable via the import function. I would prefer that we follow auto-loading conventions. -- 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.
