Vadym Chepkov

I am not sure, wasn't able to find a culrpit yet. You can easily reproduce it using a vagrant project: https://github.com/vchepkov/puppet-bootstrap ``` PUPPET_ENV=puppetdb vagrant up ```

I have compared the catalogs produced by 8.0.1 and 8.1.0 ``` puppet: Notice: /Stage[main]/Postgresql::Server::Reload/Postgresql::Server::Instance::Reload[main]/Exec[postgresql_reload_main]: Triggered 'refresh' from 1 event puppet: Notice: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Role[puppetdb]/Postgresql_psql[CREATE ROLE puppetdb ENCRYPTED PASSWORD ****]/command: changed [redacted] to...

Right, so the command create database fails and that fact doesn't get detected by puppet ``` postgres=# CREATE DATABASE "puppetdb" WITH TEMPLATE = "template0" ENCODING = 'UTF8' LC_COLLATE = 'en_US.UTF-8'...

@gdubicki , I have stumbled on this as well. branches: list is ignored. GitLabForm version: 3.6.0

property `applies_to_all_protected_branch` for the rules is ignored as well, using 3.8.0

FYI, I didn't see anything in release notes, but it seems to be working now, maybe upgrading gitlab helped?

Our current version is v16.3.7-ee. It was 15.11.13 before

@ragingra , the goal is configuring LDAP during infrastructure provisioning we have used puppet_ds module before, but changes to API made it incompatible.

This seems presumptuous https://github.com/puppetlabs/puppetlabs-peadm/blob/main/tasks/update_pe_master_rules.rb#L67 Why `result[1]` ?

I suspect, that in the background write_file function moves over a temporary file instead. It should copy file in place, this way both permissions and SELinux context would be preserved,