I am accepting the fact that the initial version of a module will not be perfect and that it will be need to be updated in the future. I am looking for ideas on how to manage the development life cycle of modules and to control the roll out of the module being applied to managed nodes. Please share your insight on what works and what doesn''t. Any reference to published documentation on this topic would be helpful too. -- 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/-/WcO8RFGm_e8J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Craig White
2012-Dec-07 18:02 UTC
Re: [Puppet Users] Best practice for updating puppet modules?
On Dec 7, 2012, at 9:07 AM, Schofield wrote:> I am accepting the fact that the initial version of a module will not be perfect and that it will be need to be updated in the future. I am looking for ideas on how to manage the development life cycle of modules and to control the roll out of the module being applied to managed nodes. Please share your insight on what works and what doesn''t. Any reference to published documentation on this topic would be helpful too.---- Pro Puppet (James Turnbull and Jeffry McCune) Craig -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.