Am Samstag, 3. Dezember 2016 18:40:58 UTC+1 schrieb Eric Sorenson:
>
> Hi Thomas, have you tried the `puppet generate type` workflow described on
> that doc to avoid the problems with environment bleed-through? You said you
> failed w/the elasticsearch module and I'm wondering if that is
Hi Thomas, have you tried the `puppet generate type` workflow described on
that doc to avoid the problems with environment bleed-through? You said you
failed w/the elasticsearch module and I'm wondering if that is because the
`generate` stuff is not working, or whether there's another part of
Hi,
> On 29 Nov 2016, at 13:31, vishcuri...@gmail.com wrote:
>
> thanks for the useful inputs,
>A solution that seems to work for us is to use a prefix as mentioned below
> with R10k.
>Puppet Master Enterprise console seems to support a feature called "Node
> Groups". It is possible to
Am Montag, 28. November 2016 19:06:55 UTC+1 schrieb Rob Nelson:
>
> This will work but I would caution against it. Only recently has per
> environment segregation been implemented and there are still some issues
> present (I believe most fixes showed up in 4.8.0 but not sure). You don't
>
This will work but I would caution against it. Only recently has per
environment segregation been implemented and there are still some issues
present (I believe most fixes showed up in 4.8.0 but not sure). You don't
want the same module at two different versions for each group being mixed
and
Hi,
> On 28 Nov 2016, at 13:32, vishcuri...@gmail.com wrote:
>
> I have a question about configuring a single Enterprise Puppet Master to
> support 2 control repos.
>
> There are 2 puppet teams who manage different puppet modules in the
> organisation that I currently work for.
>
> 1.
I have a question about configuring a single Enterprise Puppet Master to
support 2 control repos.
There are 2 puppet teams who manage different puppet modules in the
organisation that I currently work for.
1. Infrastructure Team(a.k.a Production Support Team)
- manage the
