Provide per-class config files

Registered by Stan Lagun on 2014-11-13

Sometimes class instances require cloud-specific values that cannot be embedded into Murano packages because they are immutable and thus those values cannot be modified by cloud operators.
Proposed solution is to have optional per-class config files and new property usage "Config". Properties with such usage will get their values from config file rather than from object model. Because the property would still have contract the value would be validated and contract themselves can be used to get correct config structure (for example to develop configuration UI).
Config file can be either JSON or YAML and contain dictionary propertyName->propertyValue. If it contains a record for property of non-Config usage config value will override property default

Blueprint information

Status:
Complete
Approver:
Serg Melikyan
Priority:
Medium
Drafter:
Stan Lagun
Direction:
Approved
Assignee:
Stan Lagun
Definition:
Approved
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Serg Melikyan on 2014-11-18
Completed by
Serg Melikyan on 2014-12-18

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.