See the

puppetlabs-tomcat

module at https://forge.puppet.com/puppetlabs/tomcat?src=slack&channel=forge-modules

puppetlabs-patching_as_code

v2.0.1 has been released to fix a "minor"

confine

bug that was stopping the patching_as_code fact from being properly quantified. Please remember, this is a really a community sponsored module, especially since all of the previous SEs who worked on it have gone. If anyone wants to tackle any of the other bugs or enhancements, I'll try to do my best to review PRs and release versions, but no guarantees.

See the

puppetlabs-patching_as_code

module at https://forge.puppet.com/puppetlabs/patching_as_code?src=slack&channel=forge-modules

^ maybe it’s better to transfer it to voxpupuli then?

Perforce tooling for modules CI on EL is broken? I tried to re-run CI on a PR that was fine and for which a commit was added and CI failed on all EL nodes with the very same result https://github.com/puppetlabs/puppetlabs-apache/actions/runs/13214992893?pr=2542

Or have we reached the point of no more perforce packages -> no more acceptance tests for puppetlabs modules -> puppetlabs modules are decaying?

Have there been any discussions about the puppetlabs-puppet_agent module in regard of being able to manage openvox?

See the

puppetlabs-puppet_agent

module at https://forge.puppet.com/puppetlabs/puppet_agent?src=slack&channel=forge-modules

If you use etcd or Patroni to manage HA Postgres, I’ve released new versions. Thanks for @bastelfreak and @treydock https://github.com/tailored-automation/puppet-module-patroni/blob/main/CHANGELOG.md https://github.com/tailored-automation/puppet-module-etcd/blob/main/CHANGELOG.md

Please can somebody take a look at puppetlabs/apache? The last release to the forge was 12.2.0 on 2024-10-23 Since then there has been an attempt at releasing 12.3.0 https://github.com/puppetlabs/puppetlabs-apache/commit/692ec9e2c2b960fddf4b9fca94ba3e8f424c8854 but that doesn't appear to have made it to a release. Subsequently, other changes have been merged to the main branch. Please can a new release be made as there are number of fixes to bugs such as https://github.com/puppetlabs/puppetlabs-apache/pull/2578 that broke backward compatibility? Thanks

See the

puppetlabs-apache

module at https://forge.puppet.com/puppetlabs/apache?src=slack&channel=forge-modules

Hi, On Redhat 8 based linux distributions the package repo is pointing at a CentOS packages, that hasn't been updated in months https://github.com/puppetlabs/puppetlabs-docker/pull/999 fixes this issue. Please can somebody take a look at merging that and doing a release? Thanks

Looks like we can only search modules compatible of EOL versions of Debian on the Puppet Forge…

Hey, what's the status of https://github.com/puppetlabs/puppetlabs-mysql/pull/1645? Any chance to get this merged?

I would like to add https://github.com/puppetlabs/puppetlabs-mysql/pull/1666 to the list

and https://github.com/puppetlabs/puppetlabs-mysql/pull/1667

Hi @Arpan Gupta @Amit Karsale can we consider the above PRs for merging?

hi, is there a way to bypass md5sum comment in puppetlabs-accounts module 8.2.2 for ssh_keys? It's now adding an extra key that was already managed and placed by previous module and now it's just adding this new one with comment on top...

There is an option for the user resource to purge unmanaged keys, did you set that?

it is not allowed yet in our infrastructure to completely manage authorized keys by puppet, we are working on that... but untill then this still presents a change for us on servers...

once agents are upgraded from

7.32.1

to

8.8.1

we see puppetlabs-apache is changing selinux on httpd conf files and modules, has anyone experienced anything similar to this? Module version

'12.2.0'

that was used before agent upgrade... and also seeing

Exec[remove hsts if invalid]

that wasn't there before the agent upgrade, same module version...

we still have instance with PE server

v2021.7.9

agents

7.32.1

same module version

'12.2.0'

and we don't see anything unusual there... thinking hd This started happening on part of infrastructure where we upgraded master to

2023.8.0

and agents to

8.8.1

anyone seen aything similar? Changes are mostly coming from: https://github.com/puppetlabs/puppetlabs-apache/blob/v12.2.0/manifests/init.pp#L811 but I don't see any selinux correlations there... the default context is set to:

/etc/httpd(/.*)?                                   all files          system_u:object_r:httpd_config_t:s0

but from what we see in reports it is changed to

etc_t

after the agent upgrade... this is so strange

ouh, looks like it's related to this: https://puppetcommunity.slack.com/archives/C19V5U41Z/p1740667388694119?thread_ts=1740587866.219529&cid=C19V5U41Z

Hi Modules team: https://github.com/puppetlabs/puppetlabs-apt/pull/1229 is broken on acceptance tests related to puppet packages and puppet-core I don't know what your planned next steps there are, but if someone could fix or bypass the acceptance tests, I'd appreciate it

when signing up for a forge account, the signup page forces agreement to a code of conduct that does not exist

image.png

that link redirects to a page that has no code of conduct

image.png

also redirects to the same page without code of conduct

maybe remove the requirement to agree to things that do not exist or are not available or put a code of conduct somewhere