[chef] Re: Re: Re: Notifies with an unsupported action

[Daniel DeLeo < >]

On Tue, Jan 11, 2011 at 12:22 PM, John E. Vincent (lusis)
<
 >
 wrote:
> <sorry for the top post>
>
> I agree. In lieu of any official unit testing framework, I'd rather
> have a idempotent fast-fail than a no-op on errors. I'm actually
> wishing there were support for custom logging inside those blocks to
> make debugging much easier.
>
> On Tue, Jan 11, 2011 at 3:16 PM, Noah Gibbs 
> <
 >
>  wrote:
>>  To me, it definitely makes sense to at the very least warn when an 
>> unsupported operation is given.  Mysterious no-ops are probably the most 
>> frustrating part of my current beginner experience with Chef, and tracking 
>> them down is often painful (I'm currently tracking down a mysterious no-op 
>> on "supports" with a User block and :manage_home => true, and another 
>> mysterious no-op on a cookbook_file block).

(Sorry for being so late to this party)

I think that, at minimum, Chef should check that a resource actually
defines the action you're sending via notifies. This can be done
pretty easily for the new notification syntax/internals we added in
0.9.10. Has anyone created a ticket yet?

Dan DeLeo