I also have my puppetmaster files in Subversion, and I'm running into the same problem with upgrading modules from Puppet Forge. This question on Stack Exchange (http://stackoverflow.com/q/5664666/190298) doesn't have any fancy solutions either. Here are some of the ideas I've come up with so far:
- Write a shell script to automate the process of deleting, committing, re-downloading, re-committing, so that it takes place as quickly as possible. - Set up a "QA" environment based on the same SVN repository. Do the module upgrade here and commit. Then a single "svn up" on the production files will bring them all in line. - Use git instead of subversion. It doesn't suffer from the same source tree pollution that .svn folders do. - It might be possible to have a git working copy instead of the svn working copy, but add the .git hidden folder to svn:ignore. Then git could be used to pull updates from GitHub, where most of the puppet forge modules are developed. -- Nic On Friday, 12 April 2013 05:55:52 UTC-7, Ygor wrote: > > I use Subversion to maintain the $confdir of my puppet-masters and I just > discovered that when one does an upgrade, the entire tree is blown away and > replaced -- all my .svn directories are gone. > > I see nothing in the documentation (man page and such) to address this. > > Suggestions ? > > “Sometimes I think the surest sign that intelligent life exists elsewhere > in the universe is that none of it has tried to contact us.” > Bill Waterson (Calvin & Hobbes) > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
