- From: Miquel Torres <
>
- To:
- Subject: [chef] Re: Re: Re: Announcing Little Chef
- Date: Thu, 28 Oct 2010 13:07:36 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Mz6DtBqrTaQQr+VSR10HJMjZy032joRyTH/EQlyCIeCCT2rG4DkCErJo5kb6KO7+vi f4nc5GibgNcu7s3A9CzL3evqT4dxX+KAB5nAXxHqQPJLWSU8wMXhHnY3brKgd7jcxpTo vLPHJxADLLn19E4Yfgw1NE7oHzruwEZDjeEag=
Ok, I had a look at databags. I could implement them in Little Chef,
and when calling chef-solo "merge" the data in the bags with recipe
attributes and pass it in a merged node.json file. But that is
complicating things a bit too much, and behaviour would not be
guaranteed to be identical to a Chef Server.
The best thing would be if it were implemented in Chef Solo itself.
You would call chef-solo in the same way as now, but cookbooks would
be able to use databags stored locally in "/tmp/chef-solo/databags/"
What do you think? Are there any prospects of that happening?
2010/10/28 Haselwanter Edmund
<
>:
>
>
>
Sent from my iPad
>
>
On 27.10.2010, at 18:19, Brian Akins
>
<
>
>
wrote:
>
>
>
>
> Now if we had a way to "fake" databags this would be perfect...
>
>
Yes. And fake them for chef-solo too. Could be as simple as a "databag"
>
json-node in the json-tree
Archive powered by MHonArc 2.6.16.