You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just pulled puppet-r10k version 14.0.0 to our puppet servers. Running the updated modules it doesn't seem to update the webhook-go package to 2.8.0 even though I thought it should do so according to the changelog. As far as I can see r10k::webhook::package it only ensures that webhook-go is installed but not which version. Or am I missing something?
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 8.10.0
Ruby: ruby-3.0.7-162.el9_4.x86_64
Distribution: AlmaLinux 9.5
Module version: 14.0.0
How to reproduce (e.g Puppet code you use)
Using 13.0.0 with webhook-go 2.2.0 and then updating the module to 14.0.0.
The text was updated successfully, but these errors were encountered:
The package resource has ensure => present set. Setting it to ensure => latest, manually removing the file /tmp/webhook-go.rpm and triggering a puppet run will upgrade the package to 2.8.0.
The file in /tmp won't be updated, as soon as it's downloaded once. This might be solved by adding a checksum (obviously, those differ for rpm and deb packages) or adding a version number to the file name.
The package resource won't do much, if there's no newer package downloaded first. Both latest and the version should help, as long as the first issue has been resolved.
I have just pulled puppet-r10k version 14.0.0 to our puppet servers. Running the updated modules it doesn't seem to update the webhook-go package to 2.8.0 even though I thought it should do so according to the changelog. As far as I can see
r10k::webhook::package
it only ensures thatwebhook-go
is installed but not which version. Or am I missing something?Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Using 13.0.0 with webhook-go 2.2.0 and then updating the module to 14.0.0.
The text was updated successfully, but these errors were encountered: