# Noop or dry run of chef-client

**URL:** <https://discourse.chef.io/t/noop-or-dry-run-of-chef-client/1513>\
**Category:** Chef Infra (archive)\
**Created:** [August 26, 2010, 4:20pm UTC](https://discourse.chef.io/t/noop-or-dry-run-of-chef-client/1513 "2010-08-26T16:20:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Le\_Huy](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@Le\_Huy](https://discourse.chef.io/u/Le_Huy)\
**Post date:** [August 26, 2010, 4:20pm UTC](https://discourse.chef.io/t/noop-or-dry-run-of-chef-client/1513/1 "2010-08-26T16:20:40Z")

</div>

Hi all

I need to implement simple noop i.e dry run of chef-client as we want to  
know what resources chef-client is going to modify.

I know that noop mode is not available at this time but we are not  
seeking a fancy, comprehensive, generic solution,  
we need just for a couple of resources, mostly cookbook file .

I thought that I can monkey patch resource provider but I am not sure,  
if this is a right way,

Does anyone has any idea on that issue ?

* * *

## ATTENTION: The information in this electronic mail message is private and confidential, and only intended for the addresses. Should you receive this message by mistake, you are hereby notified that any disclosure, reproduction, distribution or use of this message is strictly prohibited. Please inform the sender by reply transmission and delete the message without copying or opening it.