Open Stack

On 07/05/13 17:29 +0100, Mark McLoughlin wrote:
>On Fri, 2013-05-03 at 10:25 -0400, Monty Taylor wrote:
>> I agree. I believe the natural order of things is:
>>
>> - Default value in source code
>> - Overridden by value in config file
>> - Overridden by value in environment variable
>> - Overridden by value given as command line option
>>
>> Basically due to the relative permanence of each.
>
>The "permanence order" seems reversed in the case  of tools like
>nova-manage. So, maybe the solution is to have a flag which specifies
>the order and CLIs like nova-manage would set that flag, but the
>behaviour of services would stay the same.

While I see the issues here, I still think this change should happen.
A way to keep backward compatibility would be to pinned (don't kill
me) stable branches and let his change land.

I thought a bit more about the flag and I don't think having it is a
good idea. TBH, I'd be ok with it if the default behavior is giving
priority to the CLI and the flag just reverses that but, I'd
definitely prefer not having it. There should be just one way to
manage configs and CLI arguments, IMHO.

Cheers,
FF

-- 
{ name: "Flavio Percoco",
   gpg: "87112EC1", 
   internal: "8261386",
   phone: "+390687502386",
   irc: ["fpercoco", "flaper87"]}