Hi All, i am trying to understand, why variable in my puppet module is visible in one puppet env “Prod” however not visible for Live env?

This message was deleted.

I think I'm going to go with sgnl05-sssd because it supports RHEL8 variants (ie: authselect) whereas walkamongus doesn't. Thank you for your input.

This message was deleted.

waiting Content and Tooling is about to start up in #CFD8Z9A4T

I'm interested in everyone's opinions too but since winget is only desktop right now its more limited. It feels like if Microsoft brought it to server then it would have a huge shift

Puppet Content and Tooling Releases PDK 2.7.1 The Puppet Development toolkit (PDK) provides integrated testing tools and a command line interface to help you develop, validate, and test modules Where you can find it: - https://www.puppet.com/downloads/puppet-development-kit - https://community.chocolatey.org/packages/pdk/2.7.1.0 Key features/changes: · PDK Templates have been updated to 2.7.4 · Fixes an issue with duplicate build-ids for RedHat 9 packages Full release notes Feedback - https://github.com/puppetlabs/pdk/issues - https://github.com/puppetlabs/pdk-templates/issues

I'm interested in everyone's opinions too but since winget is only desktop right now its more limited. It feels like if Microsoft brought it to server then it would have a huge shift but chocolatey is well ahead in terms of content and coverage right now

This message was deleted.

This way you can just generate a cert when needed

Then this one: https://gitlab.geant.org/geant-devops/acme-web

message has been deleted

When I started it seemed an easy one, but it turned into something convoluted. I am storing private keys on Vault (accessibile as Hiera backend) and public keys on Redis (a cessible as Hiera backend). In front of Redis i have put webdis (to let clients without puppet access the keys, without having to interact with Redis). Then I wrote a web app. I wrote an application ...

So you just done that to have the public keys also in the hiera level, right? But not in hiera itself

When I started it seemed an easy one, but it turned into something convoluted. I am storing private keys on Vault (accessibile as Hiera backend) and public keys on Redis (accessible as Hiera backend). In front of Redis I have put webdis (to let clients without puppet access the keys, without having to interact with Redis). Then I wrote a web app. I wrote an application ...

The flow is: You create a certificate on hiera (yaml). Puppet runs on one ACME server (stores it onto Gluster, runs wile-coyote to upload the keys onto vault and redis). Vault has different stanzas, for different teams, and different access tokens. It works like a charm, but it was a terrible mess

meeting 🧑‍🏫Puppet Core Team is about to start up in #CFD8Z9A4T

This message was deleted.

This message was deleted.

Wondering if anyone tried installing/running RHEL8 puppetserver/puppetdb RPMs on RHEL9…?

don't cross the streams

This message was deleted.

go with RHEL8

I suspect a number of folks are waiting for RHEL9 support whilst using Puppet on their RHEL7 or RHEL8 hosts.

nah not stupid, just kind of funny in a way that we all understand 😄

i've done far worse crossing the streams before!

I'm running my homelab pm on el8 with el9 hyps

😄

Okay, thank you, everyone.

Current roadmap still has RHEL9 Server as a Q3 initiative. However, we're supposed to get new roadmaps in the next couple of days, so we might see if it moves into Q2. In any case, it won't be within the next few weeks, so I'd recommend go with RHEL8 now and migrate later.