Clean up configuration settings

Registered by Winson Chan

Currently, the various configurations are registered in ./mistral/config.py. The configurations are registered when mistral.config is referenced. Given the way the code is written, PEP8 throws referenced but not used error if mistral.config is referenced but not called in the module. In various use cases, this is avoided by using importutils to import mistral.config (i.e. https://github.com/stackforge/mistral/blob/master/mistral/tests/unit/engine/test_transport.py#L34). This implementation should break down registration code in ./mistral/config.py into separate functions for api, engine, db, etc and move the registration closer to the module where the configuration is needed.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Winson Chan
Direction:
Needs approval
Assignee:
Winson Chan
Definition:
New
Series goal:
Proposed for juno
Implementation:
Implemented
Milestone target:
milestone icon 0.0.4
Started by
Renat Akhmerov
Completed by
Renat Akhmerov

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-config-cleanup,n,z

Addressed by: https://review.openstack.org/94225
    Clean up configuration settings

Addressed by: https://review.openstack.org/97684
    Fix duplicate keystone auth_token config options

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.