- From: Jesse Nelson <
>
- To:
- Subject: [chef] Re: Re: Re: raise_unless
- Date: Fri, 16 Jul 2010 00:26:44 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=bHH1+/vLpeXM4Hr8Mlecy4ODcQ1wGhNFn7wJxS5vUqJAUYTVioPMiRboS+k6G84Lbb fE5efy3Q8ZsAFzzxDUVzqEsbvtuEnw+AOFPOuOMuud0mPTltawunJlaIrg7mWWmNqb/s CG0aSRFltIqupF8xPy3EAXqPX7ZMkBw4Zds/4=
I agree
right now I am relying on documentation and process to deal with this.
On Jul 16, 2010, at 12:03 AM, Dreamcat4 wrote:
>
On Fri, Jul 16, 2010 at 6:37 AM, Andrew Shafer
>
<
>
>
wrote:
>
>
>
> I have some configurations where there is not really a sensible default and
>
> I want to ensure the cookbook parameters are pushed down from another
>
> cookbook or role.
>
>
+1
>
>
When cookbooks depend on each other, theres some situations where its
>
best to share certain attributes between the cookbooks. So having
>
raise_unless (or an equivalent) seems like a good idea.
>
>
dreamcat4
>
Archive powered by MHonArc 2.6.16.