- From: Caleb Tennis <
>
- To:
- Subject: [chef] Re: A case for 'run once' recipes
- Date: Wed, 23 Sep 2009 11:10:00 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; b=Xwmq9yTiBB1T6qSqJNQr7g3z5C9gms4gBP/JEg4ZY4C5YT53t2QvlwTmOjezTD5nAr HtDkADxhAgnMbIi1o0thxa3ohvzcohTbcq+J9XKwuH1m+PaJVu3CxZn1n1N/kBMVzYJl wPD6bfr9Se9XCTWbBL1D8c8oghzaH/fH5KhQc=
Spawning new clouds repaidly with chef is only one of its possible use cases, maintaining them is another. Chef would gain a lot of traction and support in the greater ISP arena if these 'run once' features are implemented.
Are you looking for something more complicated than adding a not_if into your current recipe sets? I have a lot of "run once" recipes in this fashion.
Or, you can just put a big if() around the recipe blocks. The whole thing is just interpreted ruby.
Caleb |
Archive powered by MHonArc 2.6.16.