[chef] Re: Re: Re: Re: CHEF-3506 - Don't save the node object when using an override run list?

[Daniel DeLeo < >]

On Tuesday, September 17, 2013 at 6:57 AM, Elvin Abordo wrote:

I will throw my 2 pences into the fire. 

I don't think we should save the override run_list back to the node.

The current behavior is that the original run_list gets set back on the node before Chef saves it at the end of the run. There is a bug where manually saving the node during a recipe will overwrite the run_list and we've accepted a patch for that.

What we're asking here is whether all node saves should be skipped when using an override run_list. The reasoning for this is that node attributes that other recipes rely on for search may get removed by running chef with an override run_list. While we can special case a few important ones, we cannot know in advance all of the attributes that are important to your particular cookbooks, so in any case, saving the node at the end of the run _could_ lead to incorrect configuration elsewhere.

-- 

Daniel DeLeo