I'd love to see you write an article about this if there's not one already.
I think these are pretty common workflow issues people grapple with.
Rich
On Thu, Aug 18, 2016 at 9:24 AM Rob Nelson wrote:
> The term 'environment' is overloaded. In the context of puppet, I prefer
> to think of it as
:/ is this a bug?
Should I report it somewhere? o post this question somewhere else?
Thanks for your help!
Julio
On Tuesday, August 16, 2016 at 6:29:22 PM UTC-5, Julio Guevara wrote:
>
> All puppet agent have on puppet.conf
> noop = true
>
> I need to make sure that some classes (like the class t
Hi,
shameless self-plug: you could try out my r10k fork
https://github.com/xorpaul/g10k
It does the almost all operations in parallel which can speed up your
environment deployment dramatically.
Already compiled binary blobs can be found here:
https://github.com/xorpaul/g10k/releases
On Tue
On Monday, August 8, 2016 at 8:30:27 PM UTC-7, Garrett Honeycutt wrote:
>
> On 8/5/16 9:12 PM, Geoff Nichols wrote:
> >
> >
> > On Friday, July 29, 2016 at 5:00:26 PM UTC-7, Geoff Nichols wrote:
> >
> > Because Ruby 2.1 is approaching end-of-life (upstream bugfix support
> > ended M
I have followed the instructions
here:
https://docs.puppet.com/pe/2016.2/console_classes_groups.html#creating-environment-node-groups.
This states that ALL environments that are created should be a child under
"production". This makes sense because I would want it to inherit all of
the defa
