-
-
Notifications
You must be signed in to change notification settings - Fork 579
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
API /api/v1/analysis - PUT call does not populate analisisDetail #3470
Comments
@nscuro , currently their is details Column in Analysis table The changes will involve creating new table for details which will store analysis Id, details text, and timestamp. For below details. 14 Feb 2024 at 12:15:16 P.S. I'm not sure if Frontend is handled for this. If not, this will need to be handled separately. It will involve maintaining backward compatibility, which can be done by ensuring that |
@surajbora59 This shouldn't require a new table at all. As you found out, the This appears to be caused by this code: dependency-track/src/main/java/org/dependencytrack/resources/v1/AnalysisResource.java Lines 159 to 171 in 91afc7d
If no |
…nalysis added either via UI or directly via REST call. Does add more comments when using the UI but reflects state of the vulnerability audit better. Fixes: DependencyTrack#3470 Signed-off-by: Sebastien Delcoigne <[email protected]>
…is comments modifications Signed-off-by: Sebastien Delcoigne <[email protected]>
…d service Adds analysis comments for justification, state and details for new analysis added either via UI or directly via REST call. Fixes DependencyTrack#3470 Signed-off-by: Sebastien Delcoigne <[email protected]>
Signed-off-by: Sebastien Delcoigne <[email protected]>
…sisService to avoid "Object with id 'x' is managed by a different persistence manager" error types Signed-off-by: Sebastien Delcoigne <[email protected]>
…nalysis added either via UI or directly via REST call. Does add more comments when using the UI but reflects state of the vulnerability audit better. Fixes: DependencyTrack#3470 Signed-off-by: Sebastien Delcoigne <[email protected]>
…d service Adds analysis comments for justification, state and details for new analysis added either via UI or directly via REST call. Fixes DependencyTrack#3470 Signed-off-by: Sebastien Delcoigne <[email protected]>
Signed-off-by: Sebastien Delcoigne <[email protected]>
…sisService to avoid "Object with id 'x' is managed by a different persistence manager" error types Signed-off-by: Sebastien Delcoigne <[email protected]>
… AnalysisService to avoid "Object with id 'x' is managed by a different persistence manager" error types Signed-off-by: Sebastien Delcoigne <[email protected]>
…nalysis added either via UI or directly via REST call. Does add more comments when using the UI but reflects state of the vulnerability audit better. Fixes: DependencyTrack#3470 Signed-off-by: Sebastien Delcoigne <[email protected]>
…d service Adds analysis comments for justification, state and details for new analysis added either via UI or directly via REST call. Fixes DependencyTrack#3470 Signed-off-by: Sebastien Delcoigne <[email protected]>
Signed-off-by: Sebastien Delcoigne <[email protected]>
… AnalysisService to avoid "Object with id 'x' is managed by a different persistence manager" error types Signed-off-by: Sebastien Delcoigne <[email protected]>
Current Behavior
I noticed that analysisDetails text is delivered as expected and populated in Details box but it is not actually "pushed" to the Audit Trail.
Steps to Reproduce
curl -k -X PUT "$BASE_URL" \ -H "Content-Type: application/json" \ -H "X-Api-Key: $API_KEY" \ -d "{ \"project\": \"$PROJECT_ID\", \"component\": \"$COMPONENT_ID\", \"vulnerability\": \"$VUUID\", \"analysisState\": \"EXPLOITABLE\", \"analysisResponse\": \"NOT_SET\", \"analysisDetails\": \"MY TEXT HERE\", \"isSuppressed\": false }"
2. Access WebUI
3. Investigate Audit Trial section // observe Details section
Expected Behavior
Audit Trial should have a full record from API transaction, AnalysisState works as expected, AnalysisDetais does not.
14 Feb 2024 at 12:15:16
Analysis: NOT_SET → EXPLOITABLE
14 Feb 2024 at 12:15:16
Details: MY TEXT HERE
Dependency-Track Version
4.9.x
Dependency-Track Distribution
Container Image
Database Server
PostgreSQL
Database Server Version
No response
Browser
Google Chrome
Checklist
The text was updated successfully, but these errors were encountered: