nice: https://github.com/mmckinst/puppet-lint-legacy_facts-check/blob/master/lib/puppet-lint/plugins/legacy_facts.rb#L29-L98

nice: https://github.com/mmckinst/puppet-lint-legacy_facts-check/blob/master/lib/puppet-lint/plugins/legacy_facts.rb#L29-L98

So Essentially I install this linter on my local dev box and run the cmdline to have it automatically search through the manifests and replace legacy facts.... that is nice! Top Scope facts was going to be another one and that gave me a link to that linter...Thank you!

This message was deleted.

Yes, but I want for CI to work with the old environment while i’m testing. Can my

master

branch be associated with puppet6 server and

puppet7

branch with puppet7 server?

okay, but where would I specify that

puppet7

environment must be associated with puppet7 server..?

I have multiple environments.

master

stays for now on puppet6.domain.com.

puppet7

is now should be associated with puppet7.domain.com.

that was what I was suggesting in my first response. You will need to deploy environments to the puppet7 server eventually, and very likely you will want to deploy to both simultaneously as part of the migration. Go ahead and figure that out now; then you will have the environments on both servers, and use git to manage changes

Hello All, I would like to get notifications whenever a new version for puppetserver or puppet releases also if any new vulnerability is there for existing version including the remediation Can someone please suggest me how I can achieve it ?

IIRC there was an RSS feed for vulnerabilities at least..

This message was deleted.

Hello 🙂 do we have any specific date for release of puppet on bookworm ? Debian's puppet has different setup than official's

I think there's no fix date yet

This message was deleted.

@Igar Volan has left the channel

This message was deleted.

would have been nice if database_ini.pp used a data type that allowed string and explicitly converted to a number, like it does with some other parameters in there

that second error just looks like a bug in the PE puppet code

making a support ticket, the Product Version selection box doesn't even list 2023.3.0 😒

well, reverting to my pre-upgrade snapshot, removing the bad data in the console, running puppet on the primary, and running the upgrade installer again gives the same error. so not sure how to fix this.

used

puppet lookup

to see that the string port value is coming from

/etc/puppetlabs/enterprise/conf.d/pe.conf

just did an in-place upgrade of my PE 2023.5.0 primary server (serving about 2000 nodes) from Ubuntu 18.04 to 20.04 to 22.04 💪

Hello Folks, Trying to upgrade from Oracle Linux7&Puppetv6 over to RHEL9 + puppetv7. Wondering if someone could share their performance tuning journey here.

@Oleksandr Lytvyn has left the channel

@choffee has left the channel

@spp has left the channel

@josh has left the channel