On Thu, May 15, 2014 at 11:19:05AM -0700, Guy Knights wrote: > I'm looking at ways to better automate our build pipeline and I'm trying to > envision ways to get our latest code package onto servers, while also being > able to update this package at specific, later times. > > The code will be served from a local yum repository, so I figure we can > install the latest version on new systems using an "ensure => present" in a > package resource, and then push out updates from our bamboo server via > mcollective. I understand that it's possible to install packages directly > using mcollective via a plugin such as this one: > https://github.com/puppetlabs/mcollective-package-agent. What I also am led > to believe is that if I use the "ensure => present" in the package > resource, that puppet will not make any attempts (after the initial > install) to upgrade to a newer version of the package. > > Does this seem like a valid way to get our code onto servers, ensuring that > puppet won't run arbitrary upgrades at some random later point?
You probably want either ensure => latest or ensure => 'version number', depending on how you're pushing packaes to your repo. Stu -- >From the prompt of Stu Teasdale The more you sweat in peace, the less you bleed in war. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140515183706.GD17009%40drogna.org.uk. For more options, visit https://groups.google.com/d/optout.
