Generate 'keystone.conf.sample' dynamically

Registered by Dave Chen on 2015-02-15

'keystone.conf.sample' canbe generated by the conf registed in oslo-config, so we can provide shell script to scan the source code and generate the sample config file instead of maintain this file in the trunk, the benifit for keystone project is the single truth of source and can generate the file dynamically.

The action has been taken in the projects like 'nova' and 'cinder', the README for conf file generation like this,

# README-nova.conf.txt
"
To generate the sample nova.conf file, run the following
command from the top level of the nova directory:

tox -egenconfig
"

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
Dave Chen
Direction:
Approved
Assignee:
Dave Chen
Definition:
Approved
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Started by
Morgan Fainberg on 2015-07-16
Completed by
Morgan Fainberg on 2015-07-16

Related branches

Sprints

Whiteboard

(stevemar) this functionality exists and did so before the bp creation date.

(davechen) thanks steve, my fault, I didn't notice that, just curious that why we are still maintaining "keystone.conf.sample" in source.

https://review.openstack.org/#/c/194906/ documents this as implemented

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.