Datastore type manager move to the Datastore version manger
A datastore version should have a manager associate with it rather than the datastore type. There is nothing on a datastore version to key off of for the validation rules of configurations. We were using the datastore type manager. This is something that is specific to the setup of the system and if we move the datastore manager to the datastore version manager then we can have "shared" managers as well as a custom manager if someone so desired. This will allow for more flexibility in deployments and validations.
This is how it looks today to setup a datastore:
datastore_update MySQL mysql ""
datastore_
datastore_
This would change to:
datastore_update MySQL ""
datastore_
datastore_
(where "mysql" is the name of the manager)
enabling you in the future to do something like:
datastore_
Blueprint information
- Status:
- Complete
- Approver:
- Michael Basnight
- Priority:
- Medium
- Drafter:
- Craig Vyvial
- Direction:
- Approved
- Assignee:
- Craig Vyvial
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
- Implemented
- Milestone target:
- 2014.1
- Started by
- Craig Vyvial
- Completed by
- Michael Basnight
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
move datastore manager to the datastore version
Work Items
Dependency tree
* Blueprints in grey have been implemented.