[[chef-dev]] RE: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Notify blocks

["Noah Kantrowitz" < >]

> -----Original Message-----
> From: Adam Jacob 
> [mailto:
 
> Sent: Friday, January 07, 2011 5:17 PM
> To: Noah Kantrowitz
> Cc: Akzhan Abdulin; 
> 
 
> Subject: [[chef-dev]] Re: [[chef-dev]] Re: [[chef-dev]] Notify blocks
> 
> On Fri, Jan 7, 2011 at 9:30 AM, Noah Kantrowitz 
> <
 >
> wrote:
> > That isn't the same thing, it would a ruby block generating a
> notification,
> > not receiving one. It can certainly be done already though (see the
> link I
> > pasted) but it looks kind of clunky. There is already a precedent
> with
> > not_if and only_if of taking either a block or "something else" too.
> 
> From the link you pasted, I'm not sure I understand your use-case here,
> Noah.
> 

The use case is wanting to just have ruby code as a callback after a
resource updates. From talking to Daniel on IRC a bit I agree with him that
notifies doesn't need to be overloaded like this, but having an
"after_update" and/or "after_error" callback point on all resources that
works similarly to before_migrate (etc) callbacks on Deploy would be cleaner
and address the same issue.

--Noah