General discussion about Chef

[chef] Re: Re: apt-get update strategy


Chronological Thread 
  • From: Mason Turner < >
  • To: " " < >
  • Subject: [chef] Re: Re: apt-get update strategy
  • Date: Mon, 28 Mar 2011 07:17:56 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; b=iM1X5YOMZFQ4YV+Er1yaMzqaUIcGNAUPq7xX+vVcvtEiT6TyQJk0D0YF3YUGU126Yl ZGqsSVVCYuTM1HA7CQBeEtTIKIF+yyM1OIWeXk3X3mERMKo+b8vHycpvlK+H4UUGj+lB xTMzmRnXbCw7GhMfhy42T4JNBF+3kXQiDXnmQ=
On Mar 28, 2011, at 5:54 AM, Luke Biddell < "> > wrote:

The flag to indicate if an update has been done is stored on the node
and has to be reset at the start of each run. Is there a better way of
setting transient attributes for the run?

Take a look at node.run_state for transient storage. I stow my searches there for reuse across a few recipes. 

-- Mason Turner (mobile)

Archive powered by MHonArc 2.6.16.

§