I am curious to get the opinion of the community on how people successfully manage software versions in their puppet modules. Personally I have adopted the profile/role pattern and have the need to support many different combinations of java based middleware. My puppet environment has evolved such that each major version of software gets its own class. For example: tomcat::6_0, tomcat::7_0, java::1_6, java::1_7. The versions then propagate into the profiles: profile::tomcat::7, profile::jboss::7, etc. This strategy has been successful but I do see others taking different approaches such as having a module for a single version of software or passing in the desired version to a class as a parameter. I haven't found any documentation or blogs that really address this so was hoping to generate some comments on the subject with this forum post. Are there any puppet best practices or known anti-patterns in this space?
-- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
