just curious if this value is exposed anywhere.. so it’s possible to setup a systemd timer to implement the expiration then 🙂

using wild cards in puppetserver ca clean --certname? doesn't seem possible right

This message was deleted.

@Yury Bushmelev @vchepkov Thanks!

And a single revocation call?

puppetserver ca clean --certname $(puppetserver ca list --format json --all | jq -r '.signed | .[] .name' | tr '\n' ',')

And a single revocation call?

puppetserver ca clean --certname $(puppetserver ca list --format json --all | jq -r '.signed | .[] .name' | magic-filterning-command | tr '\n' ',')

And a single revocation call?

puppetserver ca clean --certname $(puppetserver ca list --format json --all | jq -r '.signed | .[] .name' | ... | tr '\n' ',')

puppetserver ca list --format json

FTW

This message was deleted.

anyone see any modules to manage the yaml config for google-cloud-ops-agent?

See the

google-cloud

module at https://forge.puppet.com/google/cloud?src=slack&channel=puppet

Hey! I am getting warnings like

WARN	 -> Puppet Forge module 'puppetlabs-translate' has been deprecated, visit <https://forge.puppet.com/puppetlabs/translate> for more information.

Now I have two questions: 1. I am wondering why there is no follow up module. Any suggestions? 2. How can I figure out if this module is really used in my invironment? I tend to just remove it 😂

This message was deleted.

This message was deleted.

So if a run takes 2 minutes... and a run starts at 9:30, is the next run at 10:00 or 10:02?

not sure how puppet agent acts when started as a daemon as I’m usually run it from a systemd timer.. so it starts as defined in OnCalendar there + Delays + splay (if any)

but tbh, I see no reason why this might be important.. once per 30 min is long enough

if you need it in time then you should kick it with some orchestration tool (bolt/choria)

otherwise.. ±30 min doesn’t really matter when managing thousands of servers

and if you really care you can cron puppet - which you should probably do anyway

systemd timer > cron 😛

This message was deleted.

For larger deployments, running Puppet agent as a daemon with the splay option set may be better to help distribute load of agents hitting the server over time. If using cron/systemd-timer, its going to be up to you to keep track of how many you stack oat concurrent times if concerned about spreading the load across the hour

But tbh I would not schedule Puppet agent using cron

This message was deleted.

allthethings 🧑‍🏫 Bolt is about to start up in #CFD8Z9A4T

There's a docker plugin that looks interesting but it's pretty old.

This message was deleted.

I like that my question got read in to a lot, I was just asking a general question. lol I had been assuming tha the agent's '30 minutes' restarted at the end of a run, I was clearly wrong when looking at the console. We had a bunch of VMs patch at the same time and reboot, so Puppet was running at very similar times on a lot of servers. Another engineer was complaining about CPU usage in a cluster and with my previous incorrect assumption I figured the issue was going to sort it self out after a few agent runs since the Puppet run times vary a lot on those servers.