This message was deleted.
# puppet
s
This message was deleted.
b
Thank your for your response. We are using it in a CI setup, so we’d like to use the latest versions here, but thanks for the warning. The documentation states
If no version is specified the latest version available at the time will be installed, and will be kept at that version.
Copy code
mod 'puppetlabs/apache'
No other version of the module is yet installed. It is a fresh install. So I would think it would select the latest version. After some time it actually does. So it seems that r10k or the forge needs some time after getting a new version of a module to deliver it. I don’t remember having this before. But anyway…. It works now.
d
v
correct, if fresh install you will get the latest, but it won't be updated after
but I noticed the delay between publishing module and api recognizing it as latest as well
b
@vchepkov Strange thing is that Puppet module install and upgrade however did. And after some time ( I guess 15 min to 20 min) r10k now does download the latest version. I thought they where using the same api
v
#C11LCKKQ9 is probably a better source, but today is a national holiday in USA, so folks might not reply right away. I am just bored :)
l
wait, the US gets national holidays?
v
right. and I was deliberate with USA, since there is United States of Mexico 😎
l
r10k does the equivalent to puppet's ensure => present
if you want to really really bleed, use git instead of forge with branch => main 🙂
v
I don't think that was implied. but it should be to puppet module install though
and those seems get different results
b
@Lumiere I wanted the latest version that was published on the forge. I expected r10k to use the same info as puppet module install. But somehow it doesn’t. There seem to be a sync time lapse between the data r10k is using and the data puppet module install is using.
r
R10k does some caching too, that might be it
Always pin your versions even if it’s to “latest”