Thanks Garrett - so can you confirm then that ensure = present will never
try to upgrade a package after the initial install?
On Thursday, May 15, 2014 11:39:02 AM UTC-7, Garrett Honeycutt wrote:
On 5/15/14, 11:19 AM, Guy Knights wrote:
I'm looking at ways to better automate our build
Guy,
With ensure set to present all puppet will do is ensure that the
software package is installed. Regardless of what version it will simply
validate that it is installed and if it isn't it will trigger and
install of the current version. You can then make use of 'mco package
update
Thanks Jeremy, I was pretty sure that was the behaviour but I just wanted
to confirm as I hadn't found anywhere that explicitly spelled it out.
On Friday, May 16, 2014 9:24:22 AM UTC-7, Jeremy wrote:
Guy,
With ensure set to present all puppet will do is ensure that the
software package is
Hi,
It will confirm that the package is present. If it is not present it
will attempt to install it. If it is, then no action is taken.
Br,
-g
On 5/16/14, 9:09 AM, Guy Knights wrote:
Thanks Garrett - so can you confirm then that ensure = present will
never try to upgrade a package after the
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
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
On 5/15/14, 11:19 AM, 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
