On Nov 8, 4:48 pm, Tim C <tcolli...@gmail.com> wrote: > Thanks for you help. > > Does that mean that there is no way to do it from inside of a puppet > module?
It means that there is no way at all to do it from inside Puppet that will affect the current execution of Puppet itself. Puppet does a lot of calling out to external programs, however, and if you're trying to make the environment change effective immediately for something that is performed in such a call then you may be able to do it. I'd recommend creating a custom function for that purpose; the key (Ruby) statement would be writing to the Ruby ENV hash: ENV['http_proxy'] = 'http://localhost:3128'. You can find more information on writing custom functions here: http://docs.puppetlabs.com/guides/custom_functions.html. Having said all that, I'm curious what you're trying to do that requires the environment variable to apply to anything in the current Puppet run. There might be an alternative that avoids the problem altogether. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
