Use current entity id in Aggregation Property filter
M
Mark Tarry
Another example where the proposed feature would be very useful.
Lets say we have 2 blueprints;
Service
<- Security Vuln
- Security Vulns are related to aService
- We want to use a scorecard to assign a RAG status to a Servicebased on the number of openSecurity Vulns
- To facilitate the scorecard, we create an aggregate property on Serviceto count the number of relatedSecurity Vulnentities
This all works fine, until we introduce a relationship of
Service
-> Service
- i.e. Service A has a dependency on Service B, which I'd suggest is a pretty common thing to model in the catalogue.With the new relationship established, the aggregate property starts counting all
Security Vuln
records from the source Service
entity, AND all related Service
entities.So we end up with:
- Service A (2 vulns): Total vulns = 3
- Service B (1 vuln): Total vulns = 1
Gur Shafriri
Shlomi Benita Do you have another example beside the direct relationship?
For this one specifically we need to support filtering "related to" to only result in direct relations.
S
Shlomi Benita
Gur Shafriri Also for indirect link.
lets take snyk as example.
We have repo -> project -> issue.
I want to filter only the repo-related issues by adding a mirror property of the repo identifier.
Gur Shafriri
Shlomi Benita
I get what you are saying.
In a way, you want to control the relation path retrieved by "related to" by using dynamic filters.
If I understand correctly, this will enable you to get the entities related in an upstream direction, as it requires the mirror property.
Just exploring with you, what if we would add a flag to bring only the entities related with shortest path, in case there is more than one?
This should always bring these, without setting any mirror property.