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

[Luke Biddell < >]

Absolutely, the apt-get update execute resource is not guarded in any
way. Whenever we modify the content of /etc/apt/sources.list.d/ we use
a notifies to trigger an apt-get update.

We only guard on package :install (within my custom LWRP) so on a
fully converged node we don't apt-get update at all.

On 28 March 2011 14:29, Michael Hale 
<
 >
 wrote:
> Luke,
>
> I'm thinking you would want someway to apt-get update again if you add
> or remove a repository regardless of whether or not you have already
> updated in a given chef run.
>
> On Mon, Mar 28, 2011 at 8:43 AM, Luke Biddell 
> <
 >
>  wrote:
>> 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)
>>
>