bastelfreak: okay, right, so what you would do is use public_key => $wireguard_pubkeys[notebook], or something

yes, probably

coverage says I've the untested resource File[/config.json], but I'm not yet sure where that's coming from

ahhhhhhhhhhhhhhhh

m(

puppet-lint autofix broke something

OH: autofix broke

bastelfreak: okay, hopefully last question, i hope this is not too annoying :) how disruptive is the systemd-network dependency? is it a must? does that mean that everything needs to be in networkd then? how does that work on (say) laptops (or other things) typically configured with network-manager instead (or something else like ifupdown)?

you can use networkd only for the wireguard connections, if you like

Spritzgebaeck implemented support for wgquick. that might be better suited for you

awesome, okay

i think i'll already send you a few docs update, just to clear all that stuff up for the next guy :p

sure, thanks!

bastelfreak: https://github.com/voxpupuli/puppet-wireguard/pull/68

thanks!

https://github.com/voxpupuli/puppet-vault/pull/1 should be ready for review

hi

Spritzgebaeck: o/

can I get another review for https://github.com/voxpupuli/puppet-vault/pull/1 ? acceptance tests pass as well now

ewoud: now with the proper RHEL facts: We've a script that generates EL derivates facts based on the CentOS fact sets, that would now overwrite the real RHEL ones

https://github.com/voxpupuli/facterdb/blob/master/rakelib/rhel_alts.rake this one

bastelfreak: oh that's nasty

can we just get rid of the alts script?

yeah :(

I don't know

centos has a very different versioning scheme

I think OracleLinux and Scientific really don't matter.

and now we have factsets for RHEL for recent facter versions, so that should be good for a long time

so the script is probably not required anymore?