John Warburton wrote:
> I am trying to find a workaround to get functions to work with
> environments in modules as they won't be fully supported until 0.26.x
> (http://projects.reductivelabs.com/issues/1175)
>
> I can't get the workaround in bug #1175 to work - it may only have
> worked in 0.24.x
>
> Also the workaround at the end of
> http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments
> refers to "plugins", so I am thinking it too may be a 0.24.x solution
>
> If anyone has more detailed solutions to get functions in modules to
> work with environments in 0.25.x, it would be appreciated
If you can live with having all environments share the same custom
functions and custom types, you can set the libdir parameter globally
for puppetmasterd, i.e, in either the "main" or "puppetmasterd" section
of puppet.conf. I would suggest setting it only for puppetmasterd, so
as not to "pollute" stand-alone puppet with that.
I do that, and it works in both 0.24.8 and 0.25.1. I have set it to
point to the plugins in my production environment.
When I want to test new custom functions or types, I do that with
stand-alone puppet, and run it with --libdir=PATH-TO-PLUGINS. Only
when I'm certain they work with all my manifests, do I copy them
to my puppetmaster.
Luckily, I've reached the state where I have a fairly stable set of
custom functions and types, so I don't have to play that dance very
often, but I'm still looking forward to getting #1175 fixed.
/Bellman
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
