Francois Deppierraz wrote: > Hi, > > David Schmitt wrote: > >> * Environments and the workflow surrounding them >> >> There is already UsingMultipleEnvironments, which has all the technical >> stuff. Perhaps a few sentences about how to use the production, testing, >> and development environment. > > I sketched a schema describing the use of multiple environments and git > submodules for Puppet development. > > It's available on the wiki both in both OpenOffice Draw format and PDF. > > http://reductivelabs.com/trac/puppet/attachment/wiki/PuppetVersionControl/puppetmaster-git-submodules.odg > > http://reductivelabs.com/trac/puppet/attachment/wiki/PuppetVersionControl/puppetmaster-git-submodules.pdf > > I'll be glad if it could be useful for the best practices. It currently > relies heavily on git features, but it's probably doable to sketch > something similar with other versionning tools.
The more I think about it, the more I come to believe that puppet manifests should not only be version controlled, but also have a real release and patch cycle. Using submodules would be a convenient way to specify a release when working with git. Thanks for the nice graphics :) Regards, DavidS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
