-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Work towards new API from ADR 00002-analysis-graph #1217
Conversation
3bfd817
to
72596aa
Compare
56d0bc2
to
103bc7e
Compare
9d1912e
to
106e45d
Compare
63f5663
to
e07c4f0
Compare
082556d
to
5d46cb0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (though I would say this ... this is a big set of changes ... and critical)
f88ec5f
to
78663c8
Compare
Co-authored-by: Jens Reimann <[email protected]>
Co-authored-by: JimFuller-RedHat <[email protected]>
Dropping old code in the process, which was only used for a single test case anyway, which was broken.
For "describes", it actually is the document describing the package.
Also, use constants instead of magic numbers.
78663c8
to
679a272
Compare
I rewrote a few commits to bring down the number. But I think the remaining ones make sense. Alternatively, we squash them all. Which I think makes less sense. |
@carlosthe19916 there will be some API changes with the PR. Might have an impact on the UI. |
Just to confirm there was no impact on the UI |
This is a rather large set of changes ... mostly related to implementing recommendations from docs/adrs/00002-analysis-graph
Where we normalise all directional relationships from
That is in our internal model we will only have one form of the relationship (ex. Describes instead of DescribedBy, Variants instead of VariantOf) resulting in all relationships pointing 'downward' in a directed DAG.
This normalisation to a single downward direction makes the resultant conceptual model easier to understand, easier to query and will be easier to maintain.
api/v2/analysis/root-component
andapi/v2/analysis/deps
endpointsapi/v2/analysis/component
endpointExample of new graph analysis /component/ endpoint where we
Where the nested ancestors show provenance from matched component all the way up to SPDX document describing:
Similarly It is possible to get descendants of a matched component:
Or even both
Where url params
ancestors
anddescendants
control processing depth.Closes: ##1202, 1203