Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apt keyring, choria.asc, mtime is changed on every run #344

Open
mdechiaro opened this issue Feb 6, 2024 · 1 comment
Open

Apt keyring, choria.asc, mtime is changed on every run #344

mdechiaro opened this issue Feb 6, 2024 · 1 comment

Comments

@mdechiaro
Copy link

It appears the apt key is being updated with every Puppet run and causing unnecessary reports. If I run Puppet twice in quick succession, then it shows the mtime is getting changed on the file.

Notice: /Stage[main]/Choria::Repo/Apt::Source[choria-release]/Apt::Keyring[choria.asc]/File[/etc/apt/keyrings/choria.asc]/content: content changed '{mtime}2024-02-06 10:39:07 -0600' to '{mtime}2024-02-06 10:39:29 -0600'

Can we configure this resource so it only runs if the key is missing?

@ripienaar
Copy link
Member

Ongoing discussion here choria-io/general#47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants