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

[Bryan Berry < >]

My gut agrees w lusis.

Avoiding unwanted behavior should really be dealt with via disciplined use if git. If enterprise customers have big chef servers with too many sysadmins and too many cookbooks uploaded, I think they might be better served by having multiple chef servers

On Mar 21, 2012 8:22 PM, "John Vincent" <lusis.org+ " target="_blank"> > wrote:

On Wed, Mar 21, 2012 at 3:06 PM, Bryan McLellan < " target="_blank"> > wrote:
> Let's talk about this patch and what the design gives us versus what
> it locks us into.
>
> -----------
> http://tickets.opscode.com/browse/CHEF-2988 - Run List Modifiers
>
> Provides three new options to modify run lists:
>
> --allowed-recipes: Restricts what recipes are allowed in the run list
> to only those provided. This restriction is not applied to recipe
> dependencies.
> --restricted-recipes: Restricts provided recipes from running. If a
> restricted recipe is a dependency of another recipe, neither are
> allowed to run.
> --override-runlist: Replaces the current run list with provided run
> list. This override is only applied for the current run.
> -----------

My personal opinion is that it's a hack and encourages bad practice.
If your client runs are slow, fix that. If you don't trust your runs,
fix that. This is a path of madness and surprises all the way around.

Again, personal opinion.