https://github.com/voxpupuli/puppet-elastic_stack/pull/54 and the release

we can drop ubuntu16. I think that would help

that's already eol

Yeah, Ubuntu 16.04 has no chance of working anymore. CentOS can, but the test suite is quite crappy and each test break the next one… idempotency…

Well Ubundu 16.04 should be able to work with system packages but the module really likes to rely on third-party packages

yeah drop ubuntu 16

Yep once CentOS is good I will add another PR on top of it for the ChangeLog

Also drop other EOL OS

and maybe add stable ones :-)

:D

adding ones is a good job for another PR

yep, we want nice changelogs :-)

This message was deleted.

\o/ After only 45 attempts, CI is fixed! https://github.com/voxpupuli/puppet-nginx/pull/1508

I could start working on the fixes I wanted to do initially, but will rather go out and have a beer and wait until next week to touch this :-P

I'd like to help move this PR along: https://github.com/voxpupuli/puppet-zabbix/pull/834 How do I go about doing that? Branch the branch and PR the PR?

I'd like to help move this PR along: https://github.com/voxpupuli/puppet-zabbix/pull/834 How do I go about doing that? Branch the branch and PR the PR?

could anyone give me a quick dummies overview on how to set config parameters in elasticsearch.yml in the elasticsearch module please, I may have found a bug with version 8 of elasticsearch and the compatibility of v8 of the module (looks like it was built with 7 as the lastest release) want to test my bug but can't work out the correct way to feed in params for elasticsearch.yml - thought it was the config hash, but looks like I'm wrong

Is https://github.com/voxpupuli/pdk-templates dead? If so, what is the recommended way of starting a new mod with voxpupuli machinery?

Is https://github.com/voxpupuli/pdk-templates dead? If so, what is the recommended way of starting a new mod with voxpupuli machinery?

This message was deleted.

I am not sure we have something to bootstap a repo from scratch

it isn't happy about an initialized repo with no commits but it will work on a repo with a trivial first commit in it. E.g. https://github.com/jhoblitt/puppet-modsynctest

github has repo templates too. That might also be an option

Two questions on https://github.com/voxpupuli/puppet-rabbitmq/pull/913

a) should that command really be running separately on both exists? / self.instances? I think there's a cleaner way based on some other providers, but not totally sure the easiest way to do that. b) any thoughts on how to resolve the failing unit test?

https://github.com/voxpupuli/puppet-rabbitmq/pull/912 << alternate approach, though to me, seems less reliable maybe?

ahhhh, I think I see what's happening

@bastelfreak Can certainly wait until Monday but releasing

firewalld

without needing to wait on #303 to figure out whatever it's doing would be appreciated. https://github.com/voxpupuli/puppet-firewalld/pull/326#issuecomment-1200246220