On 02/21/2013 03:23 PM, Jonathan Gazeley wrote: > > Thanks for your message. I discovered through testing that the > autoloader does not support this behaviour. I had sort of resolved to > implement your suggestion although it seems a little bit messy. > > Taking a step back, are there any better solutions? I want to achieve a > common repository of modules, and a handful of environments with > different sysadmins, who will be able to call upon the common modules, > include them, and extend them in their own environments. Surely there > must be some sort of prior art? :)
I believe that the best way to achieve this is to put your modules in source control, preferably with multiple repositories like git. Each environment can thus be a branch of the main environment. All the voodoo of keeping up-to-date etc. happens outside of puppet, which is a good thing imo. HTH, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
