-
-
Notifications
You must be signed in to change notification settings - Fork 590
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 option to deactivate old project versions on BOM upload #4532
Comments
Fixes DependencyTrack#4532 Signed-off-by: Christoffer Rumohr <[email protected]>
Could you not just update the version number on the project you're uploading into? That will also maintain all your analyses. |
Fixes DependencyTrack#4532 Signed-off-by: Christoffer Rumohr <[email protected]>
Fixes DependencyTrack#4532 Signed-off-by: Christoffer Rumohr <[email protected]>
We would like to look back in time at point x and be able too see which components where in use at that exact moment. If we update an existing project the most detailed information and especially the BOM are lost. |
So you only use the new feature to cleanup once in a while? |
The BOM upload is the last step of our CI pipelines, after the automated deployment to production. We will have this flag always set to true as we don’t have different versions of the same project „active“ at the same time. |
Ah, the new feature will deactive and not delete. Never mind, nothing to see here :-) |
Current Behavior
In a continuous delivery scenario every commit to a software project creates a new version (and therefore project) in Dependency-Track. Over time there will be hundreds of "active" versions, even though they are actually not "active".
Proposed Behavior
The
POST /v1/bom
resource has another flag in addition to the already existingisLatest
parameter:isActiveExclusively
.When both arguments are
true
all "old" versions are deactivated and do not clutter the UI anymore.Checklist
The text was updated successfully, but these errors were encountered: