[chef] Re: Re: Re: node.save?

[Ranjib Dey < >]

node.save is not invoked if the run fails, but i guess we can hack it inside a report handler and save it there.

On Fri, Sep 9, 2011 at 5:03 PM, Denis Barishev < "> > wrote:

On 09/09/2011 03:31 PM, Brian Akins wrote:

On Sep 9, 2011, at 7:16 AM, Ranjib Dey wrote:

its saved at the end of the run automatically. If you are setting an attribute in the recipe and trying to reuse it in the same recipe afterwards u make an explicit node.save call.

No, you don't have to save to use later in the same run. node.save persists it on the chef-server.  This is useful to do if you know other nodes may need this node's attributes "right away."  One case in mysql master/slave configurations that was discussed on the list in the last few days.

Thanks for clarification, Brian!

Also, correct me if I am wrong, if a chef-client run fails, then node.save is not automatically called at the end.

Yeah, this moment is still of interest, right.

Denis