What I am understanding is that people are having success building/testing/deploying the OS/Middleware/Application stack by wrapping applications in a puppet resource. Thus bringing all configuration management under puppet. This is good as it is the direction I wanted to go. I would like to shift the direction of the discussion a little bit to address how the application versions are updated in puppet. James mentioned updating hiera and Brendan mentioned pointing to a different yum repo. I am sure there are multiple other ways to solve this same problem as well. But what these solutions have in common is that an individual at some point in time has to make some change to the puppet system. Is there any tooling or API that can be leveraged to allow these changes to be made and control who makes them? This would be for integrating the update to puppet in to our enterprise release management processes.
-- 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/-/EsJpWatvCU0J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
