seems like ideally you’d want that operator to target all the nodes, just not all at once, yes?

(to be able to target)

lets just say hypothetically, while on a call with Puppet professional services, someone from Puppet was showing one of our new admins how they can send a restart command to their system via tasks but no one on the call noticed the entire puppet environment was targeted and within seconds all our computers were rebooting 😅

heh

Luckily we killed the job before it went out to all systems

yeah, interesting conundrum, how do you limit the pace, but still allow an operator to target all the nodes they need to in a non-awkward workflow

but if we did the same thing in Workspace One or Intune, we have a safeguard limit at 250 so it would warn us first indicating we are about to send out this command to over 250 systems, are you sure you want to do this? Or block it all together

gotcha, so sort of a pre-flight

yeah

that some users can override

Just something to configure on the environment level that orchestration would have certain safety limits assuming a customer wanted to impose limits

or set those limits

that would be relatively easy to do with tasks

But I know the office hours is over so I can stop bugging you @steveax 😄

plans can generate their own targets (and multiple TargetSpecs)

no, good discussion, thanks! I’ll chat with some of the other team members about it!

definitely the fault of anyone behind the keyboard but certainly would be a nice feature to have

for sure, we try to guard against those things when possible

OK, that’s a wrap for today. Thanks for the suggestions! We’ll be back in a couple of weeks. Y’all be good to yourselves in the meantime!

This message was deleted.

hello friends, the puppet-forge office hours for this week are not in my favour (5 am my time [america/chicago]) -- could one of the mods please discuss this: https://github.com/puppetlabs/puppetlabs-kubernetes/pull/551 ? its been open a while and i'd like to see it merged. we have a rather peculiar environment and the solution in that pull request would make it so that i don't need to employ quite so many hacks to expand the install base.

letsplay 🧑‍🏫Puppet Core Team is about to start up in 15 minutes

Hi folks, Core office hours are open! Have a question about open source puppet or Puppet Platform 6 & 7 releases, ask away!

We recently announced availability of nightly puppet-agent packages for macOS 12 M1 in both puppet 6 and 7 streams. For example https://nightlies.puppet.com/downloads/mac/puppet6-nightly/12.

We're also working on Ubuntu 22.04 agent support. We should have nightly builds available "any day now".

And Ubuntu 22.04 will be in the next 6.x and 7.x releases.

Also Windows 11 support is in the works. Technically, puppet-agent package can be installed on Windows 11 already, but we're working on getting it integrated into our CI system.

This message was deleted.

In facter 3, it looks like we retrieved info from https://github.com/puppetlabs/facter/blob/0e7677dc8310e02aaef9ab1d1d9cd5d938fb84de/lib/inc/internal/facts/linux/release_file.hpp#L86-L89

So I think you want to do something like this to parse that data: https://github.com/puppetlabs/facter/blob/e5ad338bb6b5909c1d84cc7a580dc5dafed77e68/lib/facter/facts/photon/os/release.rb#L20-L35