- From: Andrea Campi <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Chained dependencies management
- Date: Tue, 14 Aug 2012 11:56:15 +0200
On Fri, Aug 10, 2012 at 5:22 PM, Kevin Nuckolls
<
>
wrote:
>
My opinion (and I don't know if it's a very popular one), is that
>
include_recipe is an anti-pattern when used between cookbooks. It deeply
>
couples the implementation details of two separate cookbooks. When using
>
open sourced cookbooks that use include_recipe, you often are required to
>
use the specific cookbooks that one was written against.
>
>
My solution has been that cookbooks and recipes are to be written in
>
isolation and be heavily managed by attributes. A piece of software and _all
>
of it's dependencies_ should be wrapped up in the run_lists in one nice
>
little role. That way anyone composing a new node merely has to choose from
Hear, hear! I wholeheartedly agree.
Archive powered by MHonArc 2.6.16.