...
If a flow has three nodes, there will be three different dcae service types in inventory. How those three dcae service types will be joined is via asdcServiceId and asdcResourceId . The attribute asdcServiceId will be populated with the design time flow ID and the attribute asdcResourceId will be populated with a sequence number. The dcae service types that belong to the same flow will all have the same asdcServiceId and the asdcResourceId is to be used to determine the order of the dcae service types.
A limitation of this implementation is that it will only support sequences and not topologies.
What CLAMP will do
CLAMP will query DCAE inventory to retrieve a list of all dcae service types using the GET /dcae-service-types method and endpoint. See inventory swagger YAML for more details about API.
In handling the list of dcae service types returned, CLAMP will be able to construct the target flow by:1.
- Group the dcae service types by asdcServiceId because as mentioned above, the design time flow Id will be stored in the attribute's value
...
- Construct the flow sequence from the members of the flow group by examining the asdcResourceId which will contain an integer as a string that should be used in sorting the members
Note that the if CLAMP knows the flow ID in advance, it can have DCAE inventory filter for only dcae service types that match on a specific asdcServiceId aka flow ID using the following query:
GET /dcae-service-types?asdcServiceId=9bb854b-cafd-40b9-98a5-62d287f19622