-
-
Notifications
You must be signed in to change notification settings - Fork 588
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
Add support for component properties #3499
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
851f8b2
to
8c8a3c0
Compare
@nscuro I will implement it as soon as this is merged... I should need 1 or 2 hours to implement the missing code |
Based on DependencyTrack/dependency-track#3499 Signed-off-by: nscuro <nscuro@protonmail.com>
Based on DependencyTrack/dependency-track#3499 Signed-off-by: nscuro <nscuro@protonmail.com>
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesYou may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation Footnotes
|
Supersedes DependencyTrack#2717 Co-authored-by: Robert Kesterson <rkesters@gmail.com> Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Relates to DependencyTrack#3369 Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
This is primarily to handle CycloneDX properties which do not use namespaces. Signed-off-by: nscuro <nscuro@protonmail.com>
This extends the identity of a `ComponentProperty` to also include its value. As a consequence, encrypted values will not be supported. In order to support duplicate `groupName` / `propertyValue` pairs, the `ComponentProperty` class now has a separate `uuid` field in order to still be able to address individual properties via REST API (e.g. for deletion operations). It is no longer possible to update a `ComponentProperty` via REST API. Uniqueness of properties is now enforced across `groupName`, `propertyName`, *and* `propertyValue`. Signed-off-by: nscuro <nscuro@protonmail.com>
Also don't include project properties in BOM exports (yet). Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
For his work on the component property feature in DependencyTrack#2717. Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
Description
Adds support for component properties, similar to how project properties are supported already.
On top of being manageable via REST API, component properties are also ingested upon BOM upload.
Addressed Issue
Closes #2560
Closes #2715
Closes #2717
Closes #2991
Additional Details
Frontend PR: DependencyTrack/frontend#811
Checklist
This PR fixes a defect, and I have provided tests to verify that the fix is effectiveThis PR introduces changes to the database model, and I have added corresponding update logicThis PR introduces new or alters existing behavior, and I have updated the documentation accordingly