Two relationships with the same target

Description

In a blueprint when having a node with two relationships to the same node, it should either throw an error when validating the blueprint or connect the node with both relationships.

Currently for the following node:

It runs the install WF till the relationship start:

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------

Steps to reproduce:
------------------
1.
2.
3.

Expected result:
---------------

Actual result:
-------------

Why Propose Close?

None

Activity

Show:
Ofer Yarom
August 4, 2020, 7:22 AM

I believe the proper behavior would be to assign both relationships and apply them in the order in which they appear in the blueprint, one after the other. Not sure if such a mechanism exists in the graph. Adding the larger forum to solicit thoughts and comments.
(this is not 5.1, looking into 5.2 as an option)

Trammell -
August 4, 2020, 7:54 AM

can you send an example, blueprint? I have never seen the relationship look for a target node instance ID with the ID of the node. Seems like something very wrong is happening. I am also quite sure that this node template would not pass validation, because as far as I know duplicate relationship targets are not allowed.

I’m not sure I understand a valid use case when two relationships to the same node should necessary.

Assignee

Unassigned

Reporter

Jonathan Abramsohn

Severity

Medium

Target Version

5.2

Premium Only

no

Found In Version

5.0.5

QA Owner

None

Bug Type

unknown

Customer Encountered

Yes

Customer Name

c458

Release Notes

yes

Priority

None

Priority

Unprioritized
Configure