I use a combination of both solutions to achieve a similar result. I tag modules based on internal development cycle, and then I put them all on a directory on the server (e.g. /etc/puppet/modules/stable).
each module would have a version as a suffix (e.g. ssh_1.5) then I automatically build environments, which just have links to the right combination of models that i need. e.g. one production env might link ssh to /etc/puppet/modules/stable/ssh_1.5 and another to ssh_1.0. this allow me great flexibility to reuse and share the modules. hope this helps anyone. On Thu, Jan 28, 2010 at 6:50 PM, Arnauld <a.micheli...@gmail.com> wrote: > > > Also I believe there is work to implement module or class metadata which > may provide what you're > > looking for--but I'm not sure how far off that is. > > So do I. > And I think there's really a need here. > > -- > 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<puppet-users%2bunsubscr...@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-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.
