and finally https://github.com/voxpupuli/voxpupuli-rubocop/pull/75

@Robert Waffen Get lots of rest this weekend…. Next week we may try to add Foreman support to the container-puppetserver ❗ 😅 (if we get the time…)

ah nice

I try to keep up then. But maybe @bastelfreak has to help. I’m no good with foreman 😅 maybe I learn a thing or two 🤔

We have a setup on EC2, so we’ll probably try to reuse stuff from that.

rwaffen: the integration is in https://github.com/theforeman/puppet-puppetserver_foreman and I'd say it's rather small

many files in the repo, but lots of it is just boiler plate for a Puppet module

speaking of!

I already wrote https://github.com/theforeman/puppet-puppetserver_foreman/pull/24 to simplify the report processor a lot, like dropping Puppet report format version 0

https://github.com/theforeman/puppet-foreman_proxy/pull/848 started to integrate foreman into PE environments

oh interesting

Finally got through the release:prepare steps. I can't actually do the release, but https://github.com/voxpupuli/puppet-zabbix/pull/979 is running through the CI right now

Do any of y'all know of a good way to maintain devfiles and devcontainers for a module,and keep them relatively in sync? I'd like to support both, but would like to minimize overhead from that.

FriedBob: can't you do that with modulesync/pdk ?

bastelfreak: That won't generate them, will it? One uses json, and the other yaml. I'm wanting to generate both formats from a common dataset so that I can then use something like pdk or modulesync to place them in the repos

ah okay

yea

FriedBob: with modulesync you can use ERB so effectively you get full control of Ruby to read some common data source

I may have to go that route. I've found lots of compare and contrast type things, and why one might be better than the other, but nothing to really help with using both.

ewoud: do you know if it's supported in foreman to submit reports for unknown nodes / would foreman create those? Or do I need the upload-facts cron first to create the nodes?

bastelfreak: there's a setting (defaults to true) that unknown nodes will be created based on the facts

okay

do I need a timer that runs /etc/puppetlabs/puppet/node.rb --push-facts or can one of the modules configure that?

there's a watcher process if needed

--watch-facts uses inotify to read the fact files as they change

ah nice

I think I've seen puppet code for this in the past days

ah foreman module I think

the enc.rb file in https://github.com/theforeman/puppet-puppetserver_foreman is the source for node.rb

ah but it doesn't set up a systemd unit or similar?