[chef] Re: RE: Re: Passing variables between recipes?

[Jeff Byrnes < >]

In that case, you can use an attribute to determine the data bag’s name. As for structure, that’s true, but it’s not unreasonable to encourage a structure resembling:

environment: {

  iam_user_name: {

    access_id: 'blah',

    secret_key: ‘xxx'

  }

}

-- 
Jeff Byrnes

Operations Engineer

EverTrue

@berkleebassist

On December 19, 2014 at 4:21:41 AM, Kevin Keane Subscription ( "> ) wrote:

Yes, I know about encrypted data bags, but it's code smell. I want the application cookbook to be generic, and not depend on a particular data bag or data bag structure.

Kevin Keane

The NetTech

http://www.4nettech.com

Our values: Privacy, Liberty, Justice

See https://www.4nettech.com/corp/the-nettech-values.html

-----Original message-----
From:  < >
Sent: Friday 19th December 2014 0:53
To:
Cc: ;
Subject: [chef] Re: Passing variables between recipes?

Data bag actually has facility to code password etc. 

So it will not be reviled. 

And it can be easily accessed from any node. And data is being saved only on Chef server side. 

--- Оригінальне повідомлення ---
Від кого: "Kevin Keane Subscription" < >
Дата: 19 грудня 2014, 10:32:46

I'm sure that this must be an FAQ but I can't really find the answer.

I am working with an application-cookbook/wrapper-cookbook pattern. Usually, in this pattern the wrapper cookbook sets up some attributes, and then calls the application cookbook to do the work.

In my case, I do not want to use attributes to pass the data from the wrapper to the application cookbook. Specifically, I dont' want the data to be saved in the node (the data in question is the password to a MySQL database).

I also would like to avoid using a data bag simply because it seems like code smell. Only the wrapper cookbook should "know" where the data is coming from.

What are my options?

Kevin Keane

The NetTech

http://www.4nettech.com

Our values: Privacy, Liberty, Justice

See https://www.4nettech.com/corp/the-nettech-values.html