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

[Christopher Brown < >]

Peter,
Good point, and I'd echo the same.  We are working internally on design for 
just that feature (ad-hoc push execution of partial / alternative run lists) 
and want to share our ideas with the community once we have a better handle 
on it.

-Chris

On Mar 22, 2012, at 3:28 PM, Peter Donald wrote:

> Hi,
> 
> It seems like this is an attempt to jury-rig something onto the chef
> model rather than changing the model. It seems like the use case is
> actually adhoc execution of commands/resource installation using the
> chef syntax? If so why not add the ability to distribute a one-shot
> command to chef clients when needed. Then these application deploys
> and/or apt-get upgrades or whatever could be run through this system
> and regular infrastructure maintenance can continue to use the
> existing approach. I think trying to merge the two approaches may lead
> to a bit of complexity when adopting chef.
> 
> The one place where I can see a useful to have an include/exclude is
> in the resolution of cookbook dependencies. I can quiet easily see
> that it is unnecessary to have a apt cookbook in a chef server if you
> are only deploying to redhat infrastructure. It would be nice to add
> an exclude and be done with it.
> 
> -- 
> Cheers,
> 
> Peter Donald