86cc00ab3d31e4d663904b411a77f5de9ca185aa
ci/woodpecker/pr/yamllint Pipeline was successful
ci/woodpecker/pr/ruby-validate Pipeline was successful
ci/woodpecker/pr/bolt-validate Pipeline was successful
ci/woodpecker/pr/puppet-lint Pipeline was successful
ci/woodpecker/pr/erb-validate Pipeline was successful
ci/woodpecker/pr/epp-validate Pipeline was successful
ci/woodpecker/pr/puppet-validate Pipeline was successful
ci/woodpecker/pr/ruby-check Pipeline was successful
A package pinned in hieradata right after its RPM lands in artifactapi is invisible to dnf until the host's 1h cached metadata expires, so the first Puppet run after a release cannot find the version. - Set metadata_expire 60s on rpm-internal/rpm-vendor and their per-release variants for AlmaLinux and Fedora - Leave upstream mirrors on the 1h default - Drop the stale expiry note in profiles::dns::updater
Description
production puppet-control repository
Languages
Puppet
65.7%
HTML
28.5%
Ruby
5.8%