Give priority to CLI args

Bug #1176817 reported by Flavio Percoco
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
oslo-incubator
Fix Released
High
Mark McLoughlin

Bug Description

Currently, oslo.config gives priority to arguments present in the config file instead of giving it to CLI defined ones.

This behavior should be changed to something more natural, that is, give CLI parameters the priority over config files.

Pls, read the m-l thread for more details:

http://lists.openstack.org/pipermail/openstack-dev/2013-May/008551.html

Changed in oslo:
assignee: nobody → Flavio Percoco (flaper87)
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :
Revision history for this message
Mark McLoughlin (markmc) wrote :

An implementation of the more obvious behaviour is here: https://review.openstack.org/29459

Basically, where a --config-file argument appears in the command line should determine the priority given to options set in the file

For example, if you have:

  --config-file foo.conf --blaa --config-file bar.conf

you want any value for 'blaa' in foo.conf to be overwritten by --blaa, but a value in bar.conf should overwrite --blaa

Changed in oslo:
assignee: Flavio Percoco (flaper87) → Mark McLoughlin (markmc)
importance: Undecided → High
status: New → In Progress
Revision history for this message
Alan Pevec (apevec) wrote :

https://review.openstack.org/29459 was merged, not sure why this wasn't propagated to LP, setting status manually

Changed in oslo:
status: In Progress → Fix Committed
Revision history for this message
Zhongyue Luo (zyluo) wrote :
Changed in oslo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.