and we use that in puppet-openvpn

See the

puppet-openvpn

module at https://forge.puppet.com/puppet/openvpn?src=slack&channel=voxpupuli

ah yes, ok

bastelfreak: I took a while, but https://github.com/voxpupuli/puppet-varnish/pull/6

bastelfreak: everything ok?

I think https://github.com/voxpupuli/puppet-varnish/pull/3 should be marked as backwards-incompatible (with a better title) and PR #4 as well. It isn't very clear what was changed since the migration to the new namespace

I think https://github.com/voxpupuli/puppet-varnish/pull/3 should be marked as backwards-incompatible (with a better title) and PR #4 as well. It isn't very clear what was changed since the migration to the new namespace

ewoud: back to my odd TLS problems last week: Turns out the customer has two Puppetservers, both with their own CA, and foreman knows only one of that

it's always DNS, or TLS… :)

Zhenech: o/

Zhenech: I've a foreman question! :D

someone changed something on foreman 3.4.1 and since then the run distribution chart is empty. all clients are known to foreman through the imported reports. "latest events" lists new reports coming in

why don't you ask the other resident foreman guru :D

I know there is a regression somewhere around empty reports

(so that these do not show up properly)

but that doesn't sound like what you describe

mhm I'm aware of https://projects.theforeman.org/issues/35833

which we also noticed since the chart is broken. before that the reports had an origin

that's the one, yeah

This message was deleted.

since the chart is named "run distribution chart for *Puppet*" it probably checks the origin?

aha!

so last week the customer already had foreman 3.4.1, but the used report processor was vendored into their puppet code and a bit older than what latest foreman configures

and that was switched to the upstream one

yeah, vendoring is bad :>

hopefully last freebsd bit from me this week: https://github.com/voxpupuli/beaker-puppet/pull/210

This message was deleted.

@Craig Gumbley you mean https://github.com/puppetlabs/puppet-lint/pull/93 ? I think this is a bug that should be addressed/fixed in puppet-lint. But I don't know enough ruby to really review it

https://github.com/voxpupuli/puppet-lint-optional_default-check/blob/master/lib/puppet-lint/plugins/check_optional_default.rb + https://github.com/voxpupuli/puppet-lint-params_not_optional_with_undef-check/blob/master/lib/puppet-lint/plugins/params_not_optional_with_undef.rb is what I had in mind

Hello so I was having a chat with customers about facterdb and PDK they had noticed the RedHat facts had been generated using centos and therefore noticed differences, I want to use this point to deliver https://tickets.puppetlabs.com/browse/FACT-3065 whereby Puppets facter release pipeline at a minimum should do Puppets supported agents (I mean we have to run testing on those images so they are allready built and there)