Allow target binding between two component properties (Sequence Design)

Idea ID 2858360

Allow target binding between two component properties (Sequence Design)

0 Votes

There is a use-case that requires target binding between two component properties.

I have Hybrid-2 design which allows end-users to select resource provider when subscribing. The provisioned application (AOS in this case) requires an Application Server (Tomcat) and DB (Postgres). The end-user can select in which provider the AS and DB should get provisioned. In the picture, there can be either Azure or AWS selected and the leaf nodes will provision one pair (using the Clone Pattern in the leaf node parents, only one AS and one DB is provisioned). Once the infrastructure (AS/DB) is provisioned, the AOS component (deploying application war files into AS and creating DB schema in DB) is provisioned. For AOS to work correctly, it needs to know the AS IP address and DB IP address. As the AS/DB can be one of the many leaf nodes, there can't be direct source binding between AOS AS IP Address property and multiple AS IP address properties (nor between AOS DB IP Address property and multiple DB IP address properties). Instead, it would be great to have target binding which would propagate the value from AS/DB nodes to the AOS component.

 

2021-02-22 19_05_12-Service Designer.png

 

 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.