Used a simple service two-service / one edge payload from Broadcom. It says it worked (Success message), but the data never appears.
Resolved in 24.10.1 and later
A defect (DE616099) was identified where adding edges to a service via the store API does not work when the `auto_weight=true` parameter is used. However, the store API works correctly without this parameter, but in the user case, the auto-weight feature was not applied.
The defect was fixed by updating the store API to correctly handle the `auto_weight=true` parameter, ensuring equal weight is assigned to rollups for the selected services. The fix also addressed both the UI and API, preventing the appearance of a blank screen when edges are added without attribute details. A validation check was also added to prevent the creation of circular loops in the service topology. Example payloads with and without attributes were also handled properly:
With Attributes**:
{
"targetExternalId": "Number1",
"sourceExternalId": "Number2",
"attributes": {
"health_weight": 0.5,
"risk_weight": 0.5,
"semantic": "AggregateOf"
}
}
Without Attributes**:
{
"targetExternalId": "Number1",
"sourceExternalId": "Number2"