Yah, but there are solid supportable ways to mitigate that

I’m trying to move them over to Config Data in the console, so at least it is Hiera in the console. But haven’t problems explaining how that all works

plus we have 4 separate Puppet Enterprise stacks that share a codebase, so if they do it in the console they’ll effectively have to make the same change 4 times

Well, that’s a choice they’ve made.

make their mind blown, make code that populates PE console with the arguments 🙂

from hiera

HAH!

I knew I liked you

heh… I did make a little utility to replicate a the same node group structure in all four environments

node_manager?

and then i was like “See you can do this in Git too and you can write tests around it!!

What was that thing Ranjit made for PE? The name is escaping me.

yep, node_manager

Boom.

👍

It even has a puppet face for exporting/importing node groups.

wait, I do not need to use puppet resource... for this?

checks the code

Then get that and save all that off in your “CYA Archive” too. 😄

It is a puppet resource

and PE uses

pe_node_group

I prefer Ranjit's, since his parameter is called

override_environment

vs PE's

environment_trumps

😎

This message was deleted.

Hi all, I'm installing puppet on a new client and for some reason it is excluding the subdomain and only using the tld to generate the cert. I've blown away the ssl dir on the client and cleaned the cert from the puppet server. Does anyone know why puppet is getting xyz.com rather than abc.xyz.com?

@JoeH By default it’ll use the FQDN, but if you have a value set for

certname

in puppet.conf, it’ll use that instead.

@ragnarkon the print certname is giving the tld, which is wrong, but the puppet.conf file only has environment=development set.... ?

@ragnarkon the print certname is giving the tld, which is wrong, but the puppet.conf file only has environment=development set.... ?