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

[Lamont Granquist < >]

+1 on node.run_state.  i don't know where you're getting the password 
'from' but if you don't need to persist it to the chef server, then 
don't, and just use the run_state.

On Fri Dec 19 02:17:19 2014, Tensibai Zhaoying wrote:
> See AJ message, use node.Run_state to store your values within a run
>
> Le 19 déc. 2014 10:21, Kevin Keane Subscription
> <
>  >
>  a écrit :
>
>     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