[chef] Re: RE: Re: override argument

[Daniel DeLeo < >]

On Tuesday, June 17, 2014 at 2:26 PM, Chris Sibbitt wrote:

> Did this behavior change in Chef Client 11?

We removed the node save in a recent 11.x release.
 
> 
> 
> We're still stuck on Chef 10 and the major gotcha we face with the use of 
> -o is that all the attributes from other cookbooks disappear, disrupting 
> node searches and such, just like you say. Essentially we've found that 
> while -o might come in useful, it should generally be followed by a full 
> run ASAP to prevent the corruption of the attributes and search-based 
> relationships. As such we have structured the recipes which are generally 
> -o material for us (recipes that do destructive upgrades, for example) such 
> that they always include_recipe some top-level recipe at the end, forcing a 
> more complete run to happen as part of the -o. More restrictive use of -o 
> for "partial runs" has always caused more pain then it is worth for us.
> 
> In Chef 10 all the attributes get dropped at the beginning of the run, and 
> then any new attributes from cookbooks that execute do get saved to the 
> server AFAICT. When I eventually upgrade to Chef Client 11, can I expect 
> all of my original attributes to remain unchanged after a -o run? That 
> would be awesome except for the cases where we do a node.set in the recipe 
> that is commonly used with -o....

You can manually call `node.save`, but of course that puts you back where you 
started... 

-- 
Daniel DeLeo