Puppet Community

e.g. how rspec-puppet can be used with either of them

I have not had any conversations since the last vox sync

Do you know if perforce is interested in having tools like rspec-puppet being compatible?

I would assume so, but probably best to talk during the next sync

at the sync, there is nobody from Perforce who can make decisions or speak authoritatively on anything either, at least going by the most recent sync

<@U8B8N1V2N> do you have an update on the EULA and the future of facter?

We are getting close on both of these. I should have much better updates and timing in the May monthly sync.

<@U11567REE> I digged a bit through the puppet-agent module, I think <https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/main/tasks/install_shell.sh#L123> should default to `puppet8`, not `puppet`. I think the default version should be the latest stable one. With `puppet` you just don't know what you get by default and in the past you would randomly get a new major version (probably different now with puppet core, but who knows)

<@U1PC2RAH0> yeah I agree, though I think that's a v5 breaking change (since `puppet` will attempt to install the unversioned release package)

and the default collection in the puppet code should match what the task does

that would also avoid the odd logic in <https://github.com/puppetlabs/puppetlabs-puppet_agent/pull/774>

I talked to Gavin about that. They need to call the install task with a versioned collection, e.g. `collection=puppet8` or `puppetcore8` The issue he was running into is we never published agent packages for noble to the unversioned repo <https://apt.puppet.com/pool/noble/puppet/p/index.html>

but they are here <https://apt.puppet.com/pool/noble/puppet8/p/puppet-agent/index.html>

Yeah but isn't the fix to publish the packages? :D

I don't know why they weren't published to the unversioned repo in the first place. But as you mentioned earlier, if you rely on the unversioned repo, you would be in for a nasty surprise if we published puppet-agent 8.0.0

yes. In the past that happened (and I thought that was intentionally)

The automation for publishing deb packages to <http://apt.puppet.com|apt.puppet.com> is a mess and since we aren't publishing packages to that repo any more, there's no real incentive to fix that one thing, given the risk of breaking everything else.

Alright folks that's a wrap see you again in 2 weeks!

\o Good day y’all - console office hour has begun!

If you have any questions/suggestions for anything related to the console, any of the console services (RBAC, Classifier, Activity Service) or the Orchestrator, etc. ask away.

Missed you yesterday. Would it be possible to add back nodes to plans in the console?
It's plenty of "real estate" and yet it's obfuscated

image.png

Hi <@U2S1MUUQ7> can you clarify what you mean by adding back nodes?

it used to show what node it was applied on

So, ^^ that screenshot is the plan Event log

Screenshot 2025-05-02 at 09.24.56.png

I can see details in the task itself, but it would be convenient to see it right in the plan execution

I don’t _think_ we’ve made any changes to that (looking at the git history now)

yeah, that component hasn’t changed in a few years unless I’m missing something

I think the issue there is the potential large number of nodes - is that often just a single node for you in those steps?

I swear I did see individual nodes before, weird, maybe backend changed ?

yeah, it's many nodes and plan does them sequentially

I swear node was listed before, similar how bolt does it

if task on few nodes - list them , otherwise says - on 10 nodes

I meant for a task run (not a plan task) we expose the nodes directly

but plan actions don’t expose the nodes until you drill down

well, it would be nice to see them :slightly_smiling_face:

yeah, trying to think of how we could expose without blowing that view up when there are lots of nodes

Oh, I can get the list, that’s not the issue, it’s the display side that is tricky in that view

yeah, something like that, maybe a popover or something

or, just an expand/collapse on the step directly

when you’re looking for individual nodes, are you more interested in the failure case?

I am more interested in how far along am I :slightly_smiling_face:

so tracking plan progress on the individual plan steps from the top plan view?

<@U11M008M7> maybe you and I could chat about possibilities on this later

OK, that’s a wrap for today - we’ll be back in a couple of weeks. Y’all be good to yourselves!

Hi folks, office hours are open for the next hour!