openstack
/
heat-translator
Code Issues Proposed changes

Do not use normative type as custom type 

Using TOSCA normative type as a custom type can result into type conflict
and should not be used as such.

Change-Id: I0554f9b0c0ead9fae6d14ddac3b688a75fb3dc1b
This commit is contained in:
sahdev zala 2017-01-11 12:39:41 -05:00
parent afee6dbfe8
commit 1ca7bbc214
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
translator/tests/data/test_tosca_flavor_and_image.yaml
View File

@ -3,7 +3,7 @@ tosca_definitions_version: tosca_simple_yaml_1_0
description: Template for deploying a server with custom properties for image, flavor and key_name.
node_types:
tosca.nodes.nfv.VDU:
tosca.nodes.nfv.MyType:
derived_from: tosca.nodes.Compute
properties:
key_name:
@ -21,7 +21,7 @@ topology_template:
node_templates:
my_server:
type: tosca.nodes.nfv.VDU
type: tosca.nodes.nfv.MyType
properties:
flavor: m1.medium
image: rhel-6.5-test-image