On Tuesday 30 Nov 2010 12:58:33 gdb wrote: > Hi, > > I'm using puppet with a centralized puppetmaster pushing config to > many client nodes. Most of the configuration files that puppet > manages are static and served via the puppet fileserver (running on > the puppetmaster). I often find myself making changes to a node's > config file, testing those changes, and then manually adding those > changes to the corresponding file on the puppetmaster. Is there any > way for me to cut out this last step? That is, does puppet have any > support for propagating config changes from a client node back to the > puppetmaster? In the case of static files, it seems that puppet has > enough information to determine which client config files should be > pushed back to the puppetmaster, so this seems at least theoretically > possible. > > Thanks, > > Greg
We use git. Make all the changes locally, test them in a VM, push the changes to GIT, pull the repos onto the pupptermaster. I'm not too sure the scenario you've just described is possible... M. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
