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

[Chris Sibbitt < >]

A bit late to this party, but our team is definitely in favor of removing the 
save when using an override. From the discussion on this list it seems nearly 
unanimous.

-----Original Message-----
From: Bryan McLellan 
[mailto:
 
 
Sent: Monday, September 16, 2013 11:50 PM
To: 

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

https://tickets.opscode.com/browse/CHEF-3506

This ticket proposes not saving the recipes and roles attributes when using 
an override run list. Dan wondered if we should save the node object at all. 
I can see being surprised in both situation; when your node object changes on 
the next normal client run (or gives non-normal search results in between) 
and when your node object doesn't change on an override run, but when you're 
using override you're heading down the path of someone who just asked for 
things to be a little sideways.

Anyone have a use case that would be upset by the node object being not saved 
at the end of an override run?

--
Bryan McLellan | opscode | technical program manager, open source
(c) 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org