where we are at now with bolt shim is that it is a bare bones minimal example to help people get started with that "shim" pattern

We know we can build a better solution we just have not prioritiezed it yet. Instead of investing more in the shim we are going to take a step back and consider a more comprehensive solution.

That sounds fantastic. Thank you for the info.

But Bolt Shim and PE are just one part of the issue. We still are not able to use

bolt command run

while using --transport pcp to run native powershell. We usually prefer using bolt directly instead of bolt shim because the output is much easier to ready but we still have all the format and syntax challenges there as well.

Would this also still fall under the more comprehensive solution in the future perhaps?

exactly yeah. The trick will be how we do RBAC on that. We will need a away to at minimum restrict a user to nodes.

we have joked before about

bolt --enterprise

lol

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

another thing you may at least try is a plan shim... Specifically deploy a plan that takes an arbitrary command and use PE to run that plan. Currently you would neeed to use orchestrator client for that

plan command($command, $nodes){
   # obviously params would need some special care
   return run_command($command, $nodes)
}

puppet plan run command "psversion" nodes='my-agents'

Ok I will take a look at that too. Thank you.

Hi folks, Have a question about open source puppet, ask away!

Reposting from the general puppet channel : https://puppetcommunity.slack.com/archives/C0W298S9G/p1683649464833209

I've got a few PRs that have been out for a while, any chance for forward motion? https://github.com/puppetlabs/facter/pull/2480 https://github.com/puppetlabs/facter/pull/2487 https://github.com/puppetlabs/facter/pull/2488

Basically I want to run

puppet ssl submit_request

and get the csr to submit to vault

@nickgw not currently, but please comment on https://tickets.puppetlabs.com/browse/PUP-10589

I realize I keep nagging on the kdump lense for RHEL9, but it does bug me : https://tickets.puppetlabs.com/browse/PA-4938

So the workaround now is use puppet agent bootstrap?

@nickgw I'm not sure what the status is for the bootstrap application. Adding support for generating a CSR should be pretty easy. Just need to update the

puppet ssl

application to call https://github.com/puppetlabs/puppet/blob/ad7d75b08dfff5e308fde199407d84308d74e538/lib/puppet/application/ssl.rb#L164-L176 and call

puts <http://csr.to|csr.to>_text

This message was deleted.

@Pat Riehecky I added the augeas lens ticket to our Q3 epic. This is a case where I really wish the community was able to reproduce our build process and contribute patches directly, but I don't know how feasible that is?

In the initial ticket I included the patch needed to the kdump lense

Ah sorry, what I meant is being able to contribute patches to https://github.com/puppetlabs/puppet-runtime/blob/master/configs/components/augeas.rb This is where we specify which version of augeas to pull in and which patches to apply.

With some of my patches to facter sitting for over a year without a review, it is hard to workup the motivation to toss another patch into yet another queue

yeah that's fair

I figured being broken on RHEL would motivate the business side of the house...

I was more curious if it's possible for community members to build our vanagon projects? I know some folks worked on making that process better, but I don't know the current state.

@Pat Riehecky I left a comment on https://github.com/puppetlabs/facter/pull/2487, let me know if that makes sense?

Also similar for https://github.com/puppetlabs/facter/pull/2480

goodnews Next up is 🧑‍🏫Puppet Forge in 42 hours