Issue #4178 has been updated by Luke Kanies. Branch set to luke/tickets/master/4178-ruby_manifests_not_autoloading
Ok, I've published a branch that has fixes, but no tests, and not really thoroughly tested. Also, it's a couple of fixes in one: * Fix autoloading from modules * Fix importing from the main manifests dir (haven't tested this) * Set '@name' and '@title' as you'd expect I also noticed that the way we're setting instance variables is currently by copying the params from the resource. My guess is that this is counter-intuitive - e.g., the new '$modulename' variable isn't a resource parameter, it's just a variable in the scope. So, it's probably a better idea to just take all of the variables in the scope and set those, rather than relying on the resource params. ---------------------------------------- Bug #4178: Ruby manifests don't autoload http://projects.puppetlabs.com/issues/4178 Author: Luke Kanies Status: Accepted Priority: High Assigned to: Category: Target version: 2.6 Affected version: 0.25.5 Keywords: Branch: luke/tickets/master/4178-ruby_manifests_not_autoloading Discovered this while writing up the release notes. :/ Basically, it works fine if you use 'puppet <manifest>.rb', but doesn't if you throw the ruby file in a module and try to autoload it or, I think, import it. I've got code that fixes it, but it's not yet thoroughly tested; I'll post once I have a ticket number. -- 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.
