I’m leaning to not saving the object at all in an override situation.
On Tue, Sep 17, 2013 at 4:49 AM, Bryan McLellan email@example.com wrote:
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
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org