On 11/09/2012 05:04 PM, Christian wrote: > Ihave some questions in terms of how to use puppet of configuration > management for software patches. My previous approach was it to create a > puppet module for each patch ... Like Patch1 includes (FileA, FileB, > FileC), Patch2 includes (FileD, FileE)... So far so good and that works > but now i have to create a Patch3 with lets say FileF and FileA > included. As you can see there will be a puppet conflict as i can't > deploy the same files within different modules. What is the right > architecture and method to manage software patches? Is it to use rpms > instead of? Or are there other ideas how to manage that with puppet.
You can do it with puppet, but it really isn't designed to do that. It's declarative nature will make you a lot of trouble trying to implement procedural tasks. So it would be much better to use technology that is designed with that specific issue at mind - and that are the packaging systems. So if you use RHEL/Fedora or derivates, by all means, you should go with RPM and not stretch the puppet to the limits with ugly hacks to accomplish things it isn't supposed to. -- 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.
