[chef] Re: A proof of concept cookbook for the on_failure Chef RFC

[Dan Razzell < >]

Nice.  A processing path for resource failures has been conspicuously absent in Chef, and workarounds require painfully awkward management of success counters.

I appreciate that, in keeping with the spirit of convergence, the on_failure attribute is designed to retry the original resource once its block completes.  But there's another, lower level use case that more closely resembles notification, only for failure.  Indeed it would be best implemented as an :on_failure option for the notifies and subscribes attributes.

That discussion would be somewhat out of scope for the on_failure RFC, except that a very similar effect could be had if on_failure supported something like a noretry option.  It would be clear from this option that the original resource was not to be retried on completion of the specified block.  Control would return to the resource, however, so that in the ordinary way, depending on the value for ignore_failure, it would either continue the recipe or raise an exception.

Thanks,
Dan

On 14-04-09 12:37 AM, Kannan Manickam wrote:

" type="cite">

I have playing with a proof of concept cookbook for the on_failure Chef RFC proposed recently. I made some good progress on that and it works for most use cases. So I just wanted to share it with everybody.

Here is the: https://github.com/arangamani-cookbooks/on_failure
I published it to the community site: http://community.opscode.com/cookbooks/on_failure

And I wrote the following blog post that explains how this works including some demonstration.
http://blog.arangamani.net/blog/2014/04/08/chef-on-failure-handler/

Thanks Steven, Paul, and Seth for providing awesome examples in the RFC.

Cheers,
Kannan.