configuration-templates should allow for versions to be stored
Registered by
Edward Konetzko
Configuration templates need to be versionable so that instances can tell if the default configuration has changed and take the appropriate actions.
For example.
1. User provs instance X with template A.
2. Provider updates template A to template B.
3. User with instance X now has an outdated configuration template.
Right now there is no way for a instance, user, provider to determine if a instance has version A or version B of the default configuration file.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Edward Konetzko
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- Accepted for future
- Implementation:
-
Unknown
- Milestone target:
-
next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
[dmakogon] As per current state of heat templates usage in Trove we should use only one template per service type. In future it should stay as it is, but somehow trove should be able to define how much parameters template needs.
(?)
