Issue #3295 has been updated by Paul Lathrop. % Done changed from 0 to 10 Affected version changed from 0.25.1 to 0.25.4
After deeper investigation, I've determined that the problem exists deeper in the code than generate(). generate makes use of Puppet::Util.execute() which doesn't have support for setting the working directory (at least as far as I can tell in my first read-through. I could use some help understanding how Puppet::Util.execute works. Hitting up puppet-dev. In good news I've ported generate() tests to rspec. ---------------------------------------- Bug #3295: generate() does not set the current working directory intuitively http://projects.puppetlabs.com/issues/3295 Author: Paul Lathrop Status: Accepted Priority: Normal Assigned to: Paul Lathrop Category: functions Target version: Affected version: 0.25.4 Keywords: generate Branch: While building a generate script which utilizes external resources, I've discovered that the working directory within the generate() script is set to /etc/puppet/rack (i.e. the working directory of Puppet itself) as opposed to the directory of the generate() script. While this may be "expected" behavior, it is non-intuitive, and I believe it should be fixed. -- 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.
