Implement pluggable functionality to tempest
Current realization of tempest hasn't pluggable functionality.
Proposal:
make tempest to look for extended files for:
1) config extension
2) exceptions extension
3) clients extensions
As result:
Much less merge conflicts.
For any purposes of new project can be cloned vanilla tempest and added new files to specific dirs,
tempest will read these files and dynamically add everything that is needed to new project.
Plug-ins for these purposes can be placed into 'contrib' dir of service-project files and then easy merge to tempest without any conflicts, only new files copied.
Blueprint information
- Status:
- Complete
- Approver:
- Sean Dague
- Priority:
- Undefined
- Drafter:
- Valeriy Ponomaryov
- Direction:
- Approved
- Assignee:
- Valeriy Ponomaryov
- Definition:
- Review
- Series goal:
- Proposed for icehouse
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Valeriy Ponomaryov
- Completed by
- Valeriy Ponomaryov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Implement pluggability for tempest (exceptions)
Addressed by: https:/
Implement pluggability for tempest (clients)
Addressed by: https:/
Implement pluggability for tempest (config)
Gerrit topic: https:/
Addressed by: https:/
Spec for making tempest pluggable
Work Items
Work items:
1) Make exceptions pluggable: DONE
2) Make config pluggable: DONE
3) Make clients pluggable: DONE