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

I have been testing chef configuration on several virtual machines.  
Then you can actually test them and then tear them down and rebuild  
them from time to time.

-Kevin

On Nov 30, 2009, at 6:43 AM, jon stuart 
<
 >
 wrote:

> Bryan McLellan wrote:
> > 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
> > it. Which while running in noop mode is probably fine because you
> > weren't going to do anything anyway, it would take a concerted effort
> > to get a full noop run working all the way through.
>
> Ah right, thanks for the clue-in. So definitely in the non-easy  
> category!
>
> I'll continue to play with Chef regardless, its strengths demand it :)
>
> Regards, jon.