Provide support for TOSCA qualified name
Bug #1452546 reported by
Sahdev Zala
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Heat Translator |
New
|
High
|
SREELAKSHMI PENTA |
Bug Description
In a TOSCA template, TOSCA entities can be provided as,
1. Full name e.g. tosca.nodes.Compute
2. Short name e.g. Compute
3. Qualified name e.g. tosca:Compute
The current implementation supports Full and Short name, the qualified name should be implemented the same way.
Changed in heat-translator: | |
importance: | Undecided → High |
Changed in heat-translator: | |
assignee: | nobody → Hansel Thomas (hansel.thomas) |
Changed in heat-translator: | |
assignee: | Hansel Thomas (hansel.thomas) → SREELAKSHMI PENTA (sreelakshmi-penta) |
To post a comment you must log in.
Looking at translator/ hot/translate_ node_templates. py /pypi.python. org/pypi/ multi_key_ dict/ or any custom multi key dict.
It seems that this aliasing could be achieved by using multi-key dicts such as https:/
e.g.
TOSCA_TO_ HOT_TYPE[ 'tosca. nodes.Compute' , 'Compute', 'tosca:Compute'] = ToscaCompute HOT_TYPE[ 'tosca. nodes.network. Network' , 'Network', 'tosca:Network'] = ToscaNetwork
TOSCA_TO_