[chef] Re: Re: apt_package_hold or preventing version critical packages from being upgraded


Chronological Thread 
  • From: Loïc Antoine-Gombeaud < >
  • To:
  • Subject: [chef] Re: Re: apt_package_hold or preventing version critical packages from being upgraded
  • Date: Fri, 21 Dec 2012 18:04:21 +0100

Not sure if that's what Brad had in mind, but you always have the option to include in your recipe:

execute "apt-get upgrade -y" do
  action :run
end

On Fri, Dec 21, 2012 at 6:01 PM, Holger Amann < " target="_blank"> > wrote:


Don't allow anyone to do that manually.  All package management should be done exclusively through Chef.  In fact, all systems management of all types should be done exclusively through Chef.

If there is ever an emergency need to have an exception to this rule, and that same emergency happens more than once, you should think about updating your Chef recipes to be able to handle that emergency so that you don't have to do that manually anymore.  Or, at the very least, you should be able to manually kick off the appropriate Chef process.


Ok, in theory, but in practice that sounds totally impossible to me. As an example - you're setting up a naked OS, and after bootstrapping you're about to install Postgres/Apache/someotherlargeservice which itself will install hundred of libraries as dependencies. If there are updates for one or more of those dependencies, how do you want to do it with chef instead of doing the upgrade step manually? Am I missing some magic chef functionality/cookbook which is able to do that?



--
Loic ANTOINE-GOMBEAUD
IT contact & DevOps Engineer

 
Plinga GmbH | Saarbrücker Straße 20/21 | 10405 Berlin | Germany
E-Mail:  " target="_blank">  | skype: loic.plinga
Cell: +49 (0) 160 922 86753

www.plinga.com

Geschäftsführer: Johannes Kreibohm, Florian Schmidt-Amelung
Eingetragen beim Amtsgericht Charlottenburg, HRB 119994



Archive powered by MHonArc 2.6.16.

§