- From: Luke Biddell <
>
- To:
- Subject: [chef] Re: Re: Re: apt-get update strategy
- Date: Mon, 28 Mar 2011 13:43:45 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=qi9QcmyKjjvFIJ8lFxf8/kl6Yu6RJJfvuQ9T7c1YsMO6PnRX5CSW1jKLNgmsNhDVw4 K7MvFgL36iyQyHemkQnfBoRh6QBRcODanHhufnTSI9ticgw0kOwNefyoS7qedkQoo6Ro i/3Uowuptjituzli58BbA3Y7dM7vbmnrxTuHM=
Perfect, just what I was looking for. Thanks.
On 28 March 2011 12:17, Mason Turner
<
>
wrote:
>
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.