Hi
Okay so what i am getting from this is.
have 2 maybe 3 environments
production - production puppet code
testing - testing modules and
dev - another testing / developer
Inside production I can use a "ENC" ? to force nodes into groups
production
sim
inf
inside there I can allocate "environme
On Friday, June 24, 2016, Alex Samad wrote:
> The point i was trying to make was not the how. But that a group of
> nodes will have 1 config and another a different config. It seems
> like environments would be the way to group that.
>
Alex,
Environment is a very overloaded term. In this case,
>> I agree but how do you make them difference for different nodes, if I
>> specify a group of nodes that have a specific MOTD... the nodes don't
>> care but ( i was using it as an example). maybe a better one would be
>> say smtp setup - all nodes have it, non prod must point to the non
>> prod s
The values they receive for a particular module parameter does not need to
have anything to do with their environment. That can come from hiera.
On Thursday, June 23, 2016, Alex Samad wrote:
> On 24 June 2016 at 00:16, jcbollinger > wrote:
> >
> >
> > On Thursday, June 23, 2016 at 1:30:37 AM UT
Hi
Might have this wrong. But..
I have puppet install - got r10k and will be using hiera
I wanted to have 1 script / programatic way of classifying scripts into
environments. I wanted to be able to look at certname and maybe ip address.
So I found this
https://docs.puppet.com/guides/external_
