you refer to upstream postgres repo's?

hmm, read 'module' instead of 'appstream' :)

yes the upstream postgres repos

Morning! Replying to a disucssion earlier this day: I/We do rely on onceover+codequality (for the control repo CI and checking outdated modules). As bastelfreak I do think that it is part of some tooling like beaker / puppet-lint / etc. that should be "community managed".

s/community/organization/ maybe… what I mean is a pool of people so that when 1 person is not available anymore, the project can continue to move on.

bastelfreak, do you have to? no. did we test anything else but the module stream? also no.

the only exception to the default module stream I ever tried uses an external postgres 13 db, works as expected

smortex: if you're interested in maintaining it a bit, I can poke people and probably get it transferred to vox pupuli

bastelfreak: yeah, maybe it's a good idea to not let it rot until the day it is utterly unusable :-)

sounds good. I will poke around

Thanks!

mhm

doesn't puppet 7.23 ship a

puppet

user anymore

I have one.

mhm

why havent I one on EL8

¯\_(ツ)_/¯

bastelfreak, puppetserver does, puppet-agent doesnt

hey all, I'm looking for a way to spin up a puppet setup to play around with https://forge.puppet.com/modules/puppet/catalog_diff. does anyone know of anything like that, so I don't have to use a "live" puppet master's catalog etc? could also be good for module development and whatnot.

Zhenech: okay I will need to check that later. the forenan puppet module tries to add the foreman user to the puppet group, but that doesnt exist

you can tell it not to by telling it you don't want puppet integration

This message was deleted.

This message was deleted.

either way, I am out for the week

have a great one

Yeah, I just did a pristine test over CentOS 8, and a blank install of the puppet-agent yields no puppet user/

everything gets installed into /opt and is owned by root

This message was deleted.