erik
06/16/2025, 3:32 PMbastelfreak
06/16/2025, 3:41 PMerik
06/16/2025, 3:42 PMbastelfreak
06/16/2025, 3:49 PMvchepkov
06/16/2025, 5:00 PMbastelfreak
06/16/2025, 5:13 PMbastelfreak
06/16/2025, 5:13 PMvchepkov
06/16/2025, 5:19 PMbastelfreak
06/16/2025, 5:23 PMmatt
06/17/2025, 7:44 AMIan CB
06/17/2025, 2:58 PMvchepkov
06/17/2025, 6:20 PMaudit => 'mtime'
on the directory, that will make it to notify an exec or a service. I don't think directory itself is "notifiable"Vivek
06/23/2025, 9:45 PMpackage { 'PACKAGE_NAME':
ensure => installed,
install_options => ['--enablerepo=REPO_NAME'],
}
But this is not working. Anyone?simonhoenscheid
06/24/2025, 5:16 AMvasunder K
06/26/2025, 10:50 AMJason St-Cyr
06/26/2025, 5:50 PMBob Negri
06/27/2025, 3:41 PMmatt
06/28/2025, 9:15 AMjms1
06/30/2025, 7:22 PMbvy9873y,Raonf
passes, but aaa111AAA!
would notBrian Schonecker
07/02/2025, 6:01 PMbastelfreak
07/02/2025, 6:03 PMbastelfreak
07/02/2025, 6:03 PMvchepkov
07/02/2025, 6:07 PMvchepkov
07/02/2025, 6:08 PMBrian Schonecker
07/02/2025, 6:11 PMmatt
07/02/2025, 6:41 PMDebug: /Stage[main]/Postgresql::Server::Passwd/Postgresql::Server::Instance::Passwd[main]/Exec[set_postgres_postgrespw_main]/unless: psql: error: FATAL: password authentication failed for user "postgres"
Debug: Exec[set_postgres_postgrespw_main](provider=posix): Executing '/usr/bin/psql -c "ALTER ROLE \"postgres\" PASSWORD ${NEWPASSWD_ESCAPED}"'
Debug: Executing with uid=postgres gid=postgres: '/usr/bin/psql -c "ALTER ROLE \"postgres\" PASSWORD ${NEWPASSWD_ESCAPED}"'
Notice: /Stage[main]/Postgresql::Server::Passwd/Postgresql::Server::Instance::Passwd[main]/Exec[set_postgres_postgrespw_main]/returns: ALTER ROLE
Notice: /Stage[main]/Postgresql::Server::Passwd/Postgresql::Server::Instance::Passwd[main]/Exec[set_postgres_postgrespw_main]/returns: executed successfully (corrective)
but I can't see a configuration change that would stop the user postgres from connecting to validate/change the password. What I'd like to do is work out what the connection string the puppet module builds up to try to authenticate so I can work backward to see which connection rule I've put in that conflicts. is there a way I can short cut getting the connection string it's using ?Oleksandr Bilko
07/03/2025, 8:05 AMsigned-by
using key['id']
in apt::source
?
Currently, with the following configuration:
apt::source { 'valkey':
ensure => 'present',
location => '<http://repo.percona.com/valkey/apt>',
repos => 'experimental',
pin => '1001',
key => {
name => 'valkey.gpg',
id => 'BCC3992DBA69042990E7527383A0F11D8507EFA5',
server => 'keyserver.ubuntu.com',
},
notify => Class['apt::update']
}
I only get this result:
# This file is managed by Puppet. DO NOT EDIT.
# valkey
deb <http://repo.percona.com/valkey/apt> bookworm experimental
Unfortunately, key['source']
is not publicly available via a URL, so it would be convenient to use the id
instead.
How can I include the signed-by
option in the generated .list
file?matt
07/03/2025, 10:07 AMBrian Schonecker
07/03/2025, 12:36 PMvkedar
07/03/2025, 1:09 PM