that should happen on each code deploy

OK so I'll guess I'll push some new branch for ther sake of deploying for now and see what happens. (edit: ...using a webhook from GitLab)

Ah, seems like a bit of confusion on my side, a ...bin/puppet code deploy also still does the trick. Sorry :D

The web hook did not trigger cleanup, and Code Manager documentation states that Code Manager does not allow for manual code deploys... guess I got lost there somewhere. Time for investigating the former and maybe for a time of... transition... set up a systemd timer fwiw

shouldn't make a difference if you trigger code deploy via the webhook or

puppet code deploy

in both cases code-manager should purge unknown environments. the purge level can also be configured

Point 1: GitLab wasn't configure to employ the webhook on a tag push event. Branch deletion does not exist as event, so there's that. A test deleting one branch and pushing a fresh other now resulted in deletion and creation inside Code Manager as well, within a minute. That was at least slower before, but all in all Code Manager still does what it has to.

btw, code manager doesn't handle deleted branch event properly, throughs a stack dump in server's log

👋 We're in the process to update from 2023.2.0 to 2023.8.3 and after running the update, the agent run fails on this:

Error: Could not retrieve catalog from remote server: Request to <https://pe-primary.xxxx:8140/puppet/v3/catalog/pe-primary.xxxx?environment=production> failed after 59.078 seconds: SSL_read: unexpected eof while reading
Wrapped exception:
SSL_read: unexpected eof while reading
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I have a case with support ongoing but if anyone saw this in the past ... 🙂

When following the docs https://help.puppet.com/pdk/current/topics/install_pdk_apt.htm i get the following error

The repository '<https://apt-puppetcore.puppet.com> noble Release' does not have a Release file.

this is with successful authentication.

<https://apt-puppetcore.puppet.com/dists/noble/>

also throws a 404. I was hoping for at least a directory listing but no luck

as far as I know, you must authenticate to access the repos. puppet core is no longer open source.

I did authenticate 🙂

I recommend to be careful with those packages anyways. If you signed the Developer EULA it doesn't allow you to work on public/open source modules

which os and version are you using?

If you signed the Developer EULA it doesn't allow you to work on public/open source modules

what the? Ugh yeah I didn't know that. What a red flag

https://github.com/voxpupuli/community-triage/issues/29 has a list of all the open pain points for the (dev) EULA

I'm fairly certain that there is nothing in the Developer EULA that would prevent you from working on public/open source modules. I'm currently working with the team to try to get something published addressing common questions and clarifications, so if there is a specific piece that you believe would block you from doing any public/open source work, please let me know so I can make sure we get that cleared up!

Please be aware that public ci is not allowed.

We're working on upgrading to PE2023 / Puppet 8, and are updating our PDK unit tests for our control repo. We have some classes where we mock functions in

pre_condition

blocks, but it seems that either

pre_condition

is not being called or the declared mock function is not in scope and we're seeing the underlying function instead in our tests. Is there some change to how

pre_condition

works with the new PDK/Puppet? I'm still early in the debugging so could be off-base but thought I'd ask before scratching my head some more...

@Jason St-Cyr> I'm fairly certain that there is nothing in the Developer EULA that would prevent you from working on public/open source modules. The dev EULA is specifically written for "internal" development, see https://github.com/voxpupuli/community-triage/issues/29#issuecomment-2658483851

PE2023.8.4 has a broken facter. Numerous custom facts now fail , for example:

(Facter) Fact resolution fact='default_route_ip', resolution='<anonymous>' resolved to an invalid value: String "192.168.1.49" contains binary data

There is no binary data there

Or this

# facter -p letsencrypt_directory
[2025-06-26 00:21:15.052285 ] ERROR Facter - Fact resolution fact='letsencrypt_directory', resolution='<anonymous>' resolved to an invalid value: String "<http://puppet.example.com|puppet.example.com>" contains binary data

Probably coming from here https://github.com/voxpupuli/puppet-letsencrypt/blob/76b319895ad5dd698acdb2ce8460c1a43e332241/lib/facter/letsencrypt_directory.rb#L24 and it's going to depend on how the name is represented (dNSName vs iPAddress). Ruby has an annoying behavior of returning a binary string for anything socket related

❯ ruby -rsocket -e 'puts Socket.gethostname.encoding'
ASCII-8BIT

I think the module should do something like

-        names = san.value.split(',').map { |entry| entry.split(':')[1] }
+        names = san.value.split(',').map { |entry| entry.split(':')[1].force_encoding(Encoding::UTF_8) }

The code works in the previous version of the LTS release and not in the new minor release. I would say it needs to be addressed in facter instead

Is there a loss of functionality? Do catalogs fail to compile?

yes, facts are empty

Is there an API or some machine readable file that can give the Puppet Agent version used in a given PE release? I'm writing a script to download what we need from https://www.puppet.com/releases whenever we're getting ready to upgrade. Doing the downloads manually is error-prone toil. So I'd like to be able to generate a URL like https://artifacts-puppetcore.puppet.com/v1/download?version=8.13.1&type=perepo-all&os_name=el&os_version=9&os_arch=x86_64 without having to parse the HTML of the release page or of https://help.puppet.com/pe/current/topics/software_components_installed.htm if possible.

My colleague @Omar Morales is making a support ticket about this, but we think that this change is preventing us from using something like

:ref => 'refs/pull/1234/merge'

for modules listed in

Puppetfile

on PE 2025.2.0, even though the commit message says "control repo". On PE 2023.8.0, which has r10k 4.1.0, using such a ref still works.