[chef-dev] Re: Re: Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes

[Adam Jacob < >]

On Wed, Mar 21, 2012 at 1:44 PM, John Vincent
<
 >
 wrote:
> 1) my runs take too long
> 2) I want to do a one off thing

So, besides the fact that some users want to do what you feel like is
a bad thing, is there a reason not to include it?

I think it's a bad idea (tm) to do one-off runs without having done a
complete converge in the near-term past (the side effects demand it!)
- but I can see the value in doing something like this for things like
triggered application deployments, where I know I want to trigger a
single subset of the run list.

My feeling is we shouldn't dismiss functionality some set of us find
useful simply out of dogmatic adherence to a model another (probably
majority) of us *do* like, unless it's really damaging to Chef. I
don't see how this is, other than being a little afraid of what
happens in infrastructure that relies on it a lot.

Nothing stops us from shipping it and making it obsolete by having a
more awesome way to do it.

Adam

-- 
Opscode, Inc.
Adam Jacob, Chief Customer Officer
T: (206) 619-7151 E: