[ARIA-356] Specifying relationship type in a node template ignores the input overrides

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.1.0, 0.1.1
• Epic Link: ARIA 1.0 Release
• Assignee: Unassigned
• Reporter: Tal Liron
• Created: 29/Aug/17 17:59
• Updated: 03/Oct/17 20:11

Description

See this example:

tosca_definitions_version: tosca_simple_yaml_1_0

data_types:

  MyData:
    properties:
      field:
        type: string
        default: default value

relationship_types:

  MyRelationship:
    interfaces:
      Configure:
        type: tosca.interfaces.relationship.Configure
        add_target:
          inputs:
            my_input:
              type: MyData

capability_types:

  MyCapability: {}

node_types:

  MyNode1:
    capabilities:
      my_capability: MyCapability

  MyNode2:
    requirements:
      - my_requirement:
          capability: MyCapability
          relationship: MyRelationship

topology_template:

  node_templates:

    my_node1:
      type: MyNode1

    my_node2:
      type: MyNode2
      requirements:
        - my_requirement:
            relationship:
              type: MyRelationship # THE PROBLEM
              interfaces:
                Configure:
                  add_target:
                    inputs:
                      my_input:
                        field: assigned value

The above will fail to parse with this error:

Validation issues:
  4: interface definition "Configure" does not assign a value to a required operation input "add_target.my_input" in "relationship"

The reason is that specifying the type (see the line with the "THE PROBLEM" comment) causes ARIA to ignore the following interface definition, so indeed the required input remains unassigned.

Commenting out the "THE PROBLEM" line will allow the service template to parse correctly.