For me, when I was deciding to manage updates, there were two options for me.
1. Set everything to ensure latest and only use clones of centos/redhat repos for different environments such as QA, and production. The downside of here is that you need to manage every package in puppet, you will probably miss some. 2. Just use ensure => present and use another solution such as spacewalk or satellite to manage updates. That is what I choose personally. It works out pretty good so far. On Tuesday, September 24, 2013 4:31:10 PM UTC-4, François Chenais wrote: > > Hello, > > I got many classes, using the well known template ... > > package > ensure => XXX > notify => service > > file > require => package > notify => service > > service > require => File, Package > > > ... with ensure value XXX set to 'latest'. > > > This implies that package could be updated when I change a value > in config file even if I don't want to update it ... especially in > production ... > > A solution can be changing all ensure value to 'present' or 'installed' > but I'm not > the owner of the code so I would like to know if there is a way to > > - deactivate the package update through a command line option ? > - change the ensure value using > > - a command line option > - a fact > - a tag > - ??? > > > > More generally, what's the best practice to manage software updates using > puppet : > > - ensure => present > - fix pkg repositories :/ > - ??? > > > Thanks a lot > > > François > > > > > > > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
