----- Original Message ----- > From: "Guillem Liarte" <guillem.lia...@googlemail.com> > To: puppet-users@googlegroups.com > Sent: Thursday, January 10, 2013 11:44:13 AM > Subject: [Puppet Users] mcollective package plugin rpm versions > > Hello, > > I am trying to find out how to manage versions for installed software. > > It seems that the 'package' plugin does not take a version argument, > rendering it quite less useful than it could be. Yes, I can manage a > version with Puppet, but maybe in certain environments I would like to be > able to manage the version of the installed software from mc. > > So what I would like to do is: > > mco package install myapp 1.1.2 -C myapp -F environment=development > > Obviously this is not possible now because package does not take versions > as an argument. > > I have tried the 'packages' plug-in that claims to manage several packages > and takes versions but, it plainly does not work (they say they tested it > with EL6, I use EL5). > > I control the version of packages with puppet/hiera currently. This is a > good solution, but I am looking to let puppet do all the work up to the > last bit, where the application version can be changed the same way as you > would o yum install package-*version*. I am not looking for how to do this > with yum or puppet, but with mcollective. > > > So, what do you guys and girls do to manage package versions for your > environments with mcollective?
it would be easy to add the ability to manage the ensure property of the package from the mcollective command line. We've not had that feature request though before now -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
