Or what you might want to do is to create a specific common directory for code that should be shared, and per-environment directories which contain code that should not be shared. If you find that something should no longer be common, you then move it into the per-env directories as appropriate.
-- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community On Thu, Jun 16, 2011 at 12:42 PM, Aaron Grewell <aaron.grew...@gmail.com>wrote: > If you want your environments to never be able to affect one another then > your module paths should not contain any common directories. > > > On Thu, Jun 16, 2011 at 12:33 PM, Gabriel Filion <lelu...@gmail.com>wrote: > >> I got further into the problem thanks to your help.. but there's >> something else now. >> >> On 11-06-15 12:36 PM, Nigel Kersten wrote: >> > > Functions get executed master side, so even though they get >> > delivered to >> > > the node, they need to be accessible on the master. >> > >> > oh, ok.. so I'd need to have that new plugin used by the master >> first? >> > >> > > What version of Puppet are you running on the master and nodes? >> > >> > master: 0.25.4 >> > node: 0.25.4 >> > >> > >> > Ah. For that version, you'll need to make sure the function is in the >> > libdir of the puppet master, as I believe that functions from >> > environments weren't accessible to the master in 0.25.x >> >> that seems to have worked. I copied the files in the master's lib dir >> and it got further. However, I'm now stuck on another weirdness between >> environments: >> >> I get an error about some resource that gets redefined between the >> init.pp from the production environment and another manifest from the >> development environment called moduledir.pp >> >> in the puppet master's config I have: >> >> [main] >> logdir=/var/log/puppet >> vardir=/var/lib/puppet >> rundir=/var/run/puppet >> ssldir=/var/lib/puppet/ssl >> environment=production >> >> [...] >> >> [development] >> >> modulepath=/etc/puppet/modules-development:/etc/puppet/modules:/usr/share/puppet/modules >> >> >> I was expecting the declaration in the [development] section to mean >> that if modules are found in the first directory, then the other dirs >> are not inspected.. But apparently this is not the case. >> >> This could lead to some nasty bugs when testing things out with such a >> mixed environment. >> Is there a work around to make the other module of the same name in the >> /etc/puppet/modules directory not influence the development environment? >> >> -- >> Gabriel Filion >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@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. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@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. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
