# Noop Resource

**URL:** <https://discourse.chef.io/t/noop-resource/2996>\
**Category:** Chef Infra (archive)\
**Created:** [July 12, 2012, 6:34pm UTC](https://discourse.chef.io/t/noop-resource/2996 "2012-07-12T18:34:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bbaugher](https://avatars.discourse-cdn.com/v4/letter/b/97f17d/32.png) [@bbaugher](https://discourse.chef.io/u/bbaugher)\
**Post date:** [July 12, 2012, 6:34pm UTC](https://discourse.chef.io/t/noop-resource/2996/1 "2012-07-12T18:34:12Z")

</div>

I was wondering if anyone has ever had a use case where they created a resource  
that does nothing itself but strings together multiple notifications using  
not\_if and only\_if to control when it runs.

In my case I want to upgrade my application and the best way to do it is to,  
stop the service, remove the application, and re-install (the service is  
automatically started later).

I have a ‘bash’ resource for installing the application and I am also using the  
service resource to control start/stop.

The best method to do this seems to be to create a execute/ruby\_block resource  
that prints ‘upgrading’ and then notifies the correct resources in order [stop,  
remove, install] if the application needs to be upgraded.

It is possible for me to modify my install resource to have it take care of  
upgrading as well but I still wouldn’t be able to use the service resource for  
stop/start since I have to stop it before the resource runs. Doing this also  
seems very un-chef like.