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.
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.
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” subscription@kkeane.com
Дата: 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.
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” <subscription@kkeane.commailto:subscription@kkeane.com>
Дата: 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.