oslo-config-generator alphabetizes options
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.config |
Fix Released
|
Medium
|
Doug Hellmann |
Bug Description
oslo-config-
For example keystone has options "public_
Also, there's port configs: admin_port=35357 and public_port=5000 which should be near the bind host.
Also, public_workers and admin_workers.
It looks like this could be simulated by putting these into different "sections", but as you can see there would be a lot of sections.
affects: | oslo-incubator → oslo.config |
Changed in oslo.config: | |
milestone: | none → next-kilo |
Changed in oslo.config: | |
assignee: | nobody → Doug Hellmann (doug-hellmann) |
Changed in oslo.config: | |
milestone: | 1.5.0 → next-kilo |
Changed in oslo.config: | |
status: | Fix Committed → Fix Released |
This was intentional behavior back when everyone had their sample configs in Git and changes were reviewed. Now that most (all?) projects aren't doing that, we could potentially stop sorting.
I don't know if that would fix this particular issue though. The reason we started sorting was that everything was being written in random order before, which meant adding one option could trigger a reorder of the entire file.