An extension to enable storing of domain specific configs in SQL
With Juno we fully support domain specific configurations, via separate domain specific configuration files. While this works fine, it can be complicated to choreograph distributing the domain specific config files along side the addition of the domain in the assignment database. It would be useful to support an option where the configuration settings for a domain were stored in, say, SQL, and hence the on-boarding of a new domain would be a simpler undertaking.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Henry Nash
- Direction:
- Needs approval
- Assignee:
- Henry Nash
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- 2015.1.0
- Started by
- Henry Nash
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add an extension to store domain specific configuration in SQL.
Addressed by: https:/
Refactor domain specific loading
Addressed by: https:/
Implement backend driver support for domain config
Addressed by: https:/
Add support for whitelisting and partial domain configs
Addressed by: https:/
Add API support for domain config
Addressed by: https:/
Enable use of database domain config
Addressed by: https:/
Enable sensitive substitutions into whitelisted domain configs
Addressed by: https:/
Mark the domain config API as experimental
Addressed by: https:/
Support upload domain config files to database
Addressed by: https:/
Fix typo in name of variable in resource router
Addressed by: https:/
Reload drivers when their domain config is updated
Addressed by: https:/
Refactor code supporting status in JSON Home
Addressed by: https:/
Update configuration documentation for domain config
Addressed by: https:/
Remove unused domain config method paramters
Addressed by: https:/
Add caching to getting of the fully substituted domain config