On Wed, Jul 27, 2016 at 08:18:37AM -0700, dsdwcal wrote:
>Hmm ok thanks for the speedy reply!
>
>In implementing R10k, we've recently transitioned from a monolithic module
>repo to individual module repos. As such, our /etc/puppet/modules folder
>used to be managed by a single git
Hmm ok thanks for the speedy reply!
In implementing R10k, we've recently transitioned from a monolithic module
repo to individual module repos. As such, our /etc/puppet/modules folder
used to be managed by a single git repo that was periodically pulled down
and synced with master. It seems sen
I don't do any central modules, but everything in an environment
modulepath. That way there's no confusion about what module may be loaded.
It also keeps the configuration as simple as can be, no environment is
special in any way.
Rob Nelson
rnels...@gmail.com
On Wed, Jul 27, 2016 at 10:06 AM, d
So relatively recently we have deployed and set up R10k to manage our
environments and modules. In terms of suggested practices, I am curios what
others are currently doing to manage their production/dev environments. It
seems logical to me to change the production puppetfile's moduledir to
man
