Anyone seen this before? Trying to modify / remove a stage and this error pops up

Just got out new license for Puppet Advanced,,,, Does uploading it to PE cover the associated CD4PE or do I need to run the bolt plan to upload the license to CD4PE? We currently don't have any pipelines which use Impact Analysis... if that helps the answer.

CD doesn't need the license, but IA does. I would go ahead and upload the license, just in case you decide you want to use IA. But, CD will work without it.

I guess I should be a little more clear... you need the license on the CD server in order to use IA. The license on the PE server does nothing except license PE itself, and tell you whether you are licensed for the other advanced features.

GM... Any news about when the next version of CD4PE will be available? Just doing some planning.. and realized one had not been released since Jan.

There is a release of both 4.x and 5.x scheduled for mid-April.

We are now on a quarterly schedule for planned releases.

Finally, we managed to complete the migration and upgrade for CD4PE 4.27.1 to v5.7. It was great learning with challenging outcomes when setting it up on an Airgapped environment.

So General Question... Standing up a new instance of CD4PE attached to a new instance of Puppet. CD4PE is v5.8 and Puppet is at 2025.2. When I try to configure either using a Token or manually configure the integration between CD4PE and Puppet, immediately I get the Red Box with "An error occurred: Please contact an Administrator" which is kind of ironic since I am the Admin... but anyways... Where can I look to find out what's wrong and what I can do to resolve such an issue. I have already verified that ports are open.

CD4PE V5.8 running on an Azure VM... there is no way to update the resolv.conf or /etc/hosts because of the Podman CNI backend... which is outdated. Anyone run into this and have a plan for adding a new DNS server to allow us to resolve our ldap server or PE server?

When impact analysis is ran, is it the primaries making the calls out to the forge or is it cd4pe?

Or both

Question .. My Bolt runner server has Internet access but I my Worker node does not. If I all I want to do grab the cd4pe_jobs module from the Forge API, can I somehow use the Bolt Runner as a proxy?

Pretty sure Impact Analysis is just a feature to block me from deploying code at this point. When it decides to fail its a couple nodes that it can't fetch info from PuppetDB for.

Hey... if there is no Data showing up on the Nodes Page of CD4PE... meaning it cannot find the # of nodes with a specific aio_agent_version.,.. What should I look into? Or is this a failure of of mixed versions... like having PE 2025.2 with CD4PE v5.8?

Why does PDK validate give different output in CD4PE than when I run it on my machine? Seems like spacing issues and indents are ignored on my workstation, but once it runs through CD4PE it shows a lot more warnings/errors

I've just kind of ignored it over that last few years... but now other people are complaining

The container CD4PE use is running 3.4 and I'm using 3.4 but seeing different results... I don't get it

Need a little help understanding whats what when it comes to cd4pe_jobs. When I perform a Puppet Module list from the command line... it lists this module in two places...one version in the modules directory under a "production" branch[etc/puppetlabs/puppetserver/code/environments/production/modules] and an older version under a modules directory under the base install (/opt/puppetlabs/puppet/modules] . We are talking PE2025.2 here. Is it possible that CD4PE is using the Base install version instead of the Production version? And is there a way to tell which version it is using?

Anyone have any idea what the deal with this is? Our tokens haven't expired yet... But we can't run IA without getting this error.

Hello, I am setting up CD4PE and am wondering the recommended approach for DR. I saw in the docs that the recommendation is to version control the bolt project, however there are secrets outside of the keys file that imnot sure how to maintain. for example, the

bolt-project.yaml

file has an auth token for Puppet Forge. Storing that in a git repo is not something that im sure follows best practices

also,

inventory.yaml

could have keys/passwords for authentication to targets

Our git repos aren't public so it totally has our forge key in there. That being said, we don't use it for DR. Our VMs get restored to our DR site and I have to modfy a network setting and Puppet CD just kind of works after that.

Anyone else have their SAML stop working after going to 5.15.0? (SOLVED)

Z release going out to fix this, likely tomorrow

So anyone thinking about upgrading to 5.15.0 that use SAML, please wait and go to 5.15.1 instead

awesome, thanks for the update!

So... anyone ever have CD not able to update the pipeline status on a gitlab merge request? We seem to have random modules not able to get their pipelines status after opening an MR and aren't really sure if its a CD issue or a Gitlab issue.

Is the ServiceNow integration for CD deprecated?

@Kris has left the channel