-
-
Notifications
You must be signed in to change notification settings - Fork 563
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
Queue tokens for project cloning #2842
Comments
Additional note: Cloning is currently not executed in a single transaction, so it's possible that a failure leaves behind an incompletely cloned project. This is sub-optimal as it is hard to detect without accessing the logs. This needs to be addressed by wrapping the entire procedure into a single database transaction. |
@nscuro I did not find a way to implement the transaction part but the token I was able to do. not sure how transactions would work while wanting to use the existing token process of the event system? |
…oning Return processing token when cloning project #2842
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Current Behavior
API request "PUT /v1/project/clone" returns response 200 with new project UUID like if operation is finished
In fact, cloning a project is a continuous process that requires copying information about the components in use from the original repository to the new
That can lead to problems like #2768 when running two continuous operations at the same time leads to unwanted results
Proposed Behavior
Return status token like
PUT /v1/bom
does.This allows to track cloning process and sync task order for Dependency Track to aviod timing conflicts
Checklist
The text was updated successfully, but these errors were encountered: