Hi, we are currently managing our puppet modules with one SVN workspace for each admin. The post commit hook script updates /etc/puppet/ directory and triggers the puppet kick of the correct server.
The problem we have with this solution is that sometimes there are many small checkins to one change, because the admin forgot to change small details in the config file, e.g. forgot to change the access logfile name of the vHost, forgot a redirect, misspelling in the comments etc. What we end up with are many micro checkins, which can be used to tell every small mistake the admin has done. What we want is a solution which lets the admin test his changes on one server without checking these changes into the "main" SVN repository. So that the SVN repository only contains the final releases of the changes. I have to say that we also manage the dev and QA servers with this puppetmaster. Would dividing of these different stages into puppet environments help us? What I really want to know is, do you understand my problem and if you had the same problem, how did you solve it? SVN branches? Multiple puppetmasters, one to test with a dedicated test SVN repository? Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/FLNYwiOI1fwJ. 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.
