modsync for _grub wasn't a lot of fun... it ended up being a team effort: https://github.com/voxpupuli/puppet-augeasproviders_grub/pull/66

looking to use

vault_lookup

module with vault kv2. have run into issues because apparently we are expecting a a json object not just a string. Does this module support KV2?

https://github.com/voxpupuli/puppet-zabbix/runs/7654523479?check_suite_focus=true#step:4:8388 Seems like

apt-transport-https

was stopped being shipped in the docker image? Would that be something to add on beaker-hostgenerator?

#1261 pdksync - (GH-cat-11) Certify Support for Ubuntu 22.04 Pull request opened by david22swan (GH-cat-11) Certify Support for Ubuntu 22.04 pdk version:

2.3.0

puppetlabs/puppetlabs-stdlib GitHub Actions: Debian-10, puppet6-nightly GitHub Actions: CentOS-8, puppet7-nightly GitHub Actions: CentOS-8, puppet6-nightly GitHub Actions: CentOS-7, puppet7-nightly GitHub Actions: CentOS-7, puppet6-nightly GitHub Actions: AlmaLinux-8, puppet7-nightly GitHub Actions: AlmaLinux-8, puppet6-nightly GitHub Actions: Setup Test Matrix ✅ 2 other checks have passed 2/10 successful checks

no, apt-transport-https idead

is dead

since Debian Buster it's a dummy package (https://packages.debian.org/buster/apt-transport-https), same for Ubuntu Bionic (https://packages.ubuntu.com/bionic/apt-transport-https)

just drop Ubuntu 16.04, it's EOL

also, I thought puppetlabs-apt took care of it

https://github.com/puppetlabs/puppetlabs-apt/blob/b33313fd5d58de39e84fc242a122b5b652732f14/manifests/source.pp#L107-L112 looks like it doesn't care about Ubuntu there, so that's the root cause

if you care about Ubuntu < 18.04, that's the place to fix it but I wouldn't bother

Yea it was removed here https://github.com/puppetlabs/puppetlabs-apt/commit/1192618d075d30a8131f8cfff6af79f42c85d6a3#diff-f49722a6d64dc1d90e245[…]208cf6ed11eb7fede94040L102

FYI: https://github.com/puppetlabs/puppetlabs-apt/commit/1192618d075d30a8131f8cfff6af79f42c85d6a3 dropped it

kind of weird to do in a .y release, but ok

Yea.. 🤷

can I get a review for https://github.com/voxpupuli/puppet_metadata/pull/56

https://github.com/puppetlabs/puppetlabs_spec_helper/pull/353 any thoughts?

👍 Looks good, the only "annoying" thing is that it repeats for every operation system and it spams the diff view, but probably we can't change that?

no, it simply reports each failure

so... i'm about to fork https://forge.puppet.com/modules/bisscuitt/conntrackd. there hasn't been a forge release in a decade, and the maintainer hasn't touched github in 5 years. i've been using a fork that i put some effort into for 3 years, but i've been pulling it from github rather than pushing it to the forge.

would it make sense for voxpupuli to adopt it? i'd prefer not to make a personal fork, but i'm happy to maintain it either way.

(my fork is https://github.com/silug/puppet-conntrackd/commits/feature_puppet6)

This message was deleted.

repo moved. https://github.com/voxpupuli/puppet-conntrackd

can I get a review for https://github.com/voxpupuli/modulesync_config/pull/790

can I get a review for https://github.com/voxpupuli/modulesync_config/pull/790