> Or take it one step further and integrate your SCM and puppet ( > http://puppetlabs.com/blog/git-workflow-and-puppet-environments/ ), and > use an ENC such as dashboard, foreman, LDAP, etc to make changing the > environment a simple data change. This combination of things is the basis > that we use to develop vet and migrate incompatible changes to the > production environment. > > Ultimately it seems you may be trying to solve a problem that is not > really a puppet problem per-se. >
You are correct the problem would be introduced by bad module code. Not really a puppet problem. We do use the git workflow and dynamic environments so your suggestion for a new environment is definitely workable. Thanks for your comments. -- 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/-/6swi478njqAJ. 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.
