[chef] Re: Delayed notifications and failure (was: Re: Monitoring chef runs)

[KC Braunschweig < >]

On Fri, Sep 7, 2012 at 6:28 PM, Daniel DeLeo 
<
 >
 wrote:
> After much discussion, we decided that the idea that chef made a promise (of
> sorts) to run an action on a resource and the benefit of ending up with a
> correctly configured system according to your policy by re-running chef
> outweighed the concerns about (possibly, temporarily) leaving a resource in
> an incorrect state. Furthermore, running an incorrect version of, or
> incorrectly configured service can also lead to severe problems, so most of
> the "win" ends up on the side of always running the notifications.

FWIW I agree. Thought seems like all could be accommodated if the new
behavior became default and you could pass another setting to the
notification (rather than :delayed or :immediately) to trigger the
current behavior instead.

KC