- From: Daniel DeLeo <
>
- To: Chris Roberts <
>
- Cc: Bryan McLellan <
>,
- Subject: [chef-dev] Re: Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes
- Date: Wed, 28 Mar 2012 16:10:29 -0700
On Wednesday, March 28, 2012 at 1:04 PM, Chris Roberts wrote:
>
>
>
However, the restricted recipes provide something that the run list
>
override cannot provide, which is disabling recipes via dependencies. This
>
can be extremely useful when it is not readily apparent where a recipe
>
inclusion is originating, especially when debugging.
To me, it seems like a totally different feature would do a better job of
addressing this use case. I could imagine, say, a compile-only mode for chef
that might explain the run list expansion process, evaluate include_recipe
statements (and explain them) and at the end you might also get a list of
resources with the attribute data filled in. That should give you enough data
to fix whatever's working incorrectly in the use case you described.
--
Dan DeLeo
- [chef-dev] Re: Re: Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, (continued)
- [chef-dev] Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, AJ Christensen, 03/26/2012
- [chef-dev] Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, Bryan McLellan, 03/28/2012
- [chef-dev] Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, Chris Roberts, 03/28/2012
- [chef-dev] Re: Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, Daniel DeLeo, 03/28/2012
- [chef-dev] Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, Peter Donald, 03/29/2012
- [chef-dev] Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, Akzhan Abdulin, 03/28/2012
Archive powered by MHonArc 2.6.16.