Hi Jon, On 02/26/2012 10:17 AM, Jonathan Proulx wrote: > Hi All, > > I'm building out my first puppet install and obviously want to > leverage modules from the forge. Since I'm using git as the VCS for > my puppet configs and most community modules are hosted on github it > seems the obvious thing to do is to use either git submodules or > subtree merging, but I haven't used those features in the past so it's > not clear to me the added features are worth the complexity over > pulling a tarball of the module into my local git. It does seem > contributing back would be easier with one of the git options .... > > anyway, what methods are you using and how do you like them? > > Thanks, > -Jon >
We use git submodules for both internal and public modules since the github repositories are often ahead of the tarballs on the forge. Make sure to have an internal mirror of any submodules you clone from github in case github is down or the owner deletes the repository. We try to use modules forked or created by puppetlabs and contribute back any features we need. Otherwise we fork a module on github configure it for our environment or improve it and push it back to github. Using git submodules allows us to share non-secret puppet code internally to devs and junior sysadmins who can then push back test branches that the Senior Sysadmins can review and merge in. Also using git/puppet environments you can branch in a submodule and test your changes quite easily and then push them to github and click the pull request button in github. :) -- William Van Hevelingen <https://github.com/blkperl>https://github.com/pdxcat -- 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.
