I'm in the process of migrating data out of my standard Puppet repositories for modules and manifests, and I'm having second thoughts about my original design. I'd appreciate any feedback you can give me.
We currently have two departments managing Puppet: Operations and Development. To prevent accidentally breaking all nodes while testing, there are two repositories we work with, namely "puppet" (the production repo) and "puppet-staging" (the testing and development repo). This allows Operations to control access to the production repo (to which Development doesn't have permission to commit changes) and maintain stability. Normally all nodes run in the "production" environment, grabbing catalogs from "puppet", but we can test things at the command line by specifying the "staging" environment, which will point them at "puppet-staging". When creating repositories for hiera data, I naturally decided to create "puppet-data" and "puppet-data-staging" repos, along the same lines as above. This means I've got 4 repositories to manage, and pushing any changes involves a lot of pushing, testing and merging. How does everyone else handle it? What problems have you run into? I'm just getting started with hiera, and my node-specific data is tightly bound to modules and manifests, so I've got a lot of work ahead of me. -- 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/-/95EKCsCxm6EJ. 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.
