On 9/30/14 7:17 PM, Tom Tucker wrote: > > I just got back from PuppetConf last week and several presenters > mentioned using more than one Git repo with Puppet. Some even recommend > having a repo per module. For our initial Puppet deployment this seems > a bit excessive. My plan was to have three repos for each of our > environments (Dev, QA and Production). The contents of these repos > would contain Puppet Enterprise directory of /etc/puppetlabs/puppet. >
Hi Tom, One big repo full of modules stops scaling pretty quickly. This path makes it impossible to work in scenario where you have multiple parties using the same code base. Without individually versioning modules, you will give up the opportunity to ever make a breaking change, because you have to appease everyone. You also quickly get into situations where you cannot deploy the newest version of the code because it changes multiple modules and one of those causes issues. It leads to long running forks that will never merge, cherry picking changes, and copy/pasting code. Avoid this at all costs and save yourself the headaches. Here's an example[1] of how I manage a bunch of modules, each in their own repo. You could then use this Puppetfile with tools such as librarian-puppet-simple, librarian-puppet, and r10k. I use this repo to track all of my 'base' or 'common' modules and then use another repo to track site specific modules. For that repo, I highly recommend r10k. [1] - https://github.com/ghoneycutt/puppet-modules Best regards, -g -- Garrett Honeycutt @learnpuppet Puppet Training with LearnPuppet.com Mobile: +1.206.414.8658 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/542B5789.5080003%40garretthoneycutt.com. For more options, visit https://groups.google.com/d/optout.
