Augment Dynamic UI with DSL object model templating
In Murano pre-0.5 days Dynamic UI rendered forms that mapped to plain object model: every additional form step simply added some attributes to the list which then was finally passed to murano-api. With the introduction of Object Inheritance & Composition object model passed to murano-api has changed: it is no more a plain list, but is a nested dictionary/list instead.
The plan is to leave forms as they are now (a sequence of steps, excluding changes addressed by https:/
Blueprint information
- Status:
- Complete
- Approver:
- Alexander Tivelkov
- Priority:
- High
- Drafter:
- Timur Sufiev
- Direction:
- Approved
- Assignee:
- Timur Sufiev
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
0.5
- Started by
- Timur Sufiev
- Completed by
- Timur Sufiev
Related branches
Related bugs
Sprints
Whiteboard
Example UI definition for Active Directory application
Version: 2
Templates:
host:
type: com.mirantis.
adminPassword: {YAQL: $.serviceConfig
name: {YAQL: interpolate(
flavor: {YAQL: $.instanceConfi
image: {YAQL: $.instanceConfi
secondaryCont
type: com.mirantis.
host: $host
Application:
type: com.mirantis.
name: {YAQL: $.serviceConfig
primaryContro
type: com.mirantis.
host: $host
secondaryCont
Forms:
- ... [unchanged]
Gerrit topic: https:/
Addressed by: https:/
Use YAQL to generate MuranoPL object model from plain data.
Addressed by: https:/
Refactor get_unit_templates method using recursive_apply helper.
Work Items
Dependency tree

* Blueprints in grey have been implemented.