Something I heard at the Summit was that folks are thinking of deprecating environment run lists.--~*~ StormeRider ~*~"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSSOn Thu, Nov 14, 2013 at 12:49 PM, Xabier de Zuazo < " target="_blank"> > wrote:
Hello DV,
On Thu, 14 Nov 2013 11:02:06 -0800
DV < " target="_blank"> > wrote:
[...]
> I want to have ability to specify something like the following in theAn old ticket related to this topic:
> role:
>
> env_attributes(
> "env-1" => {
> "database" => {
> "version" => "1.2.3"
> }
> },
> "env-2" => {
> "database" => {
> "verison" => "1.2.1"
> }
> }
> )
>
> My current solution is to use env_run_lists() to do this, but it's
> time-consuming as I have to create a new recipe each time I want to
> upgrade to new version.
>
> Does that make sense? Would anyone know how I can go about
> implementing this role functionality?
>
https://tickets.opscode.com/browse/CHEF-3441
I recommend you read the comments below. It seems that it would not be
advisable to use this feature in case of adding it to the core.
I started the implementation of this some time ago. It's actually quite
simple. But I didn't continue with it because it seemed that there was
no interest.
Regards,
--
Xabier de Zuazo Oteiza
IT System Administrator - Onddo Labs S.L.
www.onddo.com
--------------------------------------------------------------------
Public Key = http://www.onddo.com/xabier_zuazo.pub
Key Fingerprint = 8EFA 5B17 7275 5F1F 42B2 26B4 8E18 8B67 9DE1 9468
--------------------------------------------------------------------
Archive powered by MHonArc 2.6.16.