[chef] Re: Re: CHEF-13 - dry-run / no-op mode

[Matthew King < >]

Bryan McLellan 
<
 >
 writes:

> On Mon, Nov 30, 2009 at 2:28 AM, jon stuart 
> <
 >
>  wrote:
>> I was wondering about the no-op stuff hinted at in CHEF-13. For me the
>> ability to eyeball proposed changes on (a sample of) nodes is pretty
>> important, both for avoiding silly mistakes whilst learning the ropes
>> and as a checkpoint before rolling out scarily large changes.
>
> It is not implemented yet. I believe the problem is that you would
> have to write support for it into every provider individually. In the
> interim, you would have to bail on all providers that didn't support

Providers that don't provide no-op functionality need only barf when
it's asked for (controlled by the code which calls the provider)[0]. If
chef is running in op mode, legacy (as they would then become) providers
can simply run as specified, optionally emitting a warning, because
overall there'd be no change from the status quo.

Matthew

[0] It should be noted that I've never looked at the chef code so I may
well be talking out of my backside. User discretion advised.

-- 
I must take issue with the term "a mere child", for it has been my
invariable experience that the company of a mere child is infinitely
preferable to that of a mere adult.
                                           --  Fran Lebowitz