[openstack-dev] [Oslo] Give CLI the priority over config files
Flavio Percoco
flavio at redhat.com
Mon May 6 09:45:05 UTC 2013
On 03/05/13 10:50 -0400, Jay Pipes wrote:
>On 05/03/2013 10:25 AM, 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. If you are running a
>> program by hand with direct CLI options - you probably want the option
>> you give to work. If you wanted the options in the config file to
>> happen, you'd probably just start the service as usual.
>
>Agreed. This is generally the default behavior of most programs,
>including the python-gflags module that oslo.config replaced in Nova.
>
Awesome, thanks for the feedback guys!
I filed a bug in oslo to track this:
https://bugs.launchpad.net/oslo/+bug/1176817
I'd also like to know the impact this change would have throughout
OpenStack.
Are existing services actually relying on this behavior?
Cheers,
FF
--
{ name: "Flavio Percoco",
gpg: "87112EC1",
internal: "8261386",
phone: "+390687502386",
irc: ["fpercoco", "flaper87"]}
More information about the OpenStack-dev
mailing list