[chef] Re: Re: Re: Re: Announcing Little Chef

[Daniel DeLeo < >]

I think of data bags as attributes of your whole infrastructure,
things that are not particular to any node or role. The cannonical
example is administrators and their private keys. In many (most?)
organizations, all of the admins have access to all of the boxes, so
this is global state that you want to manage in one place. I'm not
against having databag support for compatibility reasons in solo, but
it's a little weird conceptually, since chef-solo is limited to a
single node view of the world.

If anyone is interested in writing databag support for chef-solo, feel
free to stop by #chef-hacking on freenode or ask on chef-dev if you
have questions about the code.

Dan DeLeo

On Thu, Oct 28, 2010 at 8:41 AM, Allan Wind
<
 >
 wrote:
> On 2010-10-28T03:40:18, Haselwanter Edmund wrote:
>> 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
>
> Why are data bags needed in the first place (when attributes are
> available)?  Without support in chef-solo it fragments recipes.
>
>
> /Allan
> --
> Allan Wind
> Life Integrity, LLC
> <http://lifeintegrity.com>
>
>