This message was deleted.

This message was deleted.

This message was deleted.

@boats has left the channel

This message was deleted.

This message was deleted.

I want to change the control repo URL in my puppet enterprise install to use a fork is that possible without reinstalling the whole thing? so far it seems to change back to the previous value after running the agent again despite changing the value in pe.conf and running

puppet infrastructure configure

puppet_enterprise::profile::master::r10k_remote"

/etc/puppetlabs/r10k/r10k.yaml

oh wait. PE?

uhh… in the console or in Hiera, you can change it. Hiera is the key you listed and if you wanted to go into the console, it’s 1. t the Puppet Enterprise Console, navigate to Nodes | Classification | PE Master | Classes Tab | puppet_enterprise:profile:master. 2. In the puppet_enterprise:profile:master class, you need to set the following parameters: • r10k_remote => ‘the git FQDN and path to the namespace/control_repo of this node.’

e.g. **git@git.example.com:cmadmin/control_repo.git**

So, however you have it configured today, either the Hiera you list or the location in the console, mdify that.

After making the change on the server, make sure to run

puppet agent -t

on the Puppet server itself.

ta!

This message was deleted.

New node_manager release to incorporate Ruby v3. Sorry if anyone was waiting: https://forge.puppet.com/modules/WhatsARanjit/node_manager/0.8.0/readme

So I'm revisiting the idea of @bastelfreak where we want to put some settings from out (or from) pe.conf into Hiera. When reading: https://www.puppet.com/docs/pe/2023.2/installing_pe.html As far as I understood the documentation, the pe.conf is read during installation/updates and then never again. Can we just take the settings we changed and put it into hiera? Are there exceptions? We don't have that many. As of now I see that we set the following:

console_admin_password
puppet_enterprise::send_analytics_data
puppet_enterprise::profile::console::display_local_time
puppet_enterprise::profile::master::check_for_updates
puppet_enterprise::profile::master::code_manager_auto_configure
puppet_enterprise::profile::master::r10k_remote
puppet_enterprise::profile::master::r10k_private_key
puppet_enterprise::profile::master::r10k_proxy
puppet_enterprise::profile::orchestrator::use_application_services
pe_install::puppet_master_dnsaltnames

Anything to keep in mind when doing that?

I disagree with the statement 'never again'. In my experience, it is pretty much used

all of them can go into hiera

the pe.conf is used during upgrades/reconfiguration as well

if you changed the PE environment from production to something else, that needs to go into pe.conf. the rest is optional in my experience and I prefer it in hiera because thats easier for version control

pe.conf is read during compiling catalog. try this on primary

puppet infrastructure tune --local --pe_conf

this will populate

pe.conf

with 'recommended' settings and then run

puppet agent -t

Ah! Good to know - we have a test Puppet Primary Server that is PE environment "test"

I applied those tuned settings on our test node and will keep an eye on it for a couple of days and then see if we apply it on the prod system

thank!

You will see references to pe.conf in

/opt/puppetlabs/puppet/modules/puppet_enterprise/hiera.yaml

This message was deleted.

This message was deleted.

This message was deleted.

What should the JSON object for the key

modules

look like when using the POST /v1/deploys API?

{"environments": ["test"], "wait": true, "modules":{ "data": "data"}}

throws a validation error.

Looks like it should be:

{"environments": ["test"], "wait": true, "modules": ["foo", "bar"]}