make config templates smarter
Registered by
Michael Basnight
Currently a template must be completely copied from the source tree and put in /etc/trove. tracking for this will become a pain for deployers who only want to change 1 or 2 values. We need a better way to allow deployers to configure just waht they want, and provide sane defaults for the other configurations. See https:/
Blueprint information
- Status:
- Complete
- Approver:
- Michael Basnight
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- Accepted for future
- Implementation:
-
Unknown
- Milestone target:
-
next
- Started by
- Completed by
- Nikhil Manchanda
Related branches
Related bugs
Sprints
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
