You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When DT is integrated with a larger CI system, the DB tends to fill up quickly which leads to performance and maintainability issues. The API currently only allows to delete 1 single project at a time, and invoking the DELETE /v1/project/{uuid} method once per project UUID is time-consuming and many times leads to stability issues, rendering the application (backend + frontend) unresponsive.
My proposal is to add a /v1/project/batchDelete method that allows for deleting a list of projects specified by their UUIDs, which would allow you to make less requests and thus reduce the load on the application.
NB: I have a patch ready that implements this behavior, and this will be the basis of an upcoming PR.
Current Behavior
When DT is integrated with a larger CI system, the DB tends to fill up quickly which leads to performance and maintainability issues. The API currently only allows to delete 1 single project at a time, and invoking the DELETE
/v1/project/{uuid}
method once per project UUID is time-consuming and many times leads to stability issues, rendering the application (backend + frontend) unresponsive.Slack discussion: https://owasp.slack.com/archives/C6R3R32H4/p1701445069732229
Proposed Behavior
My proposal is to add a
/v1/project/batchDelete
method that allows for deleting a list of projects specified by their UUIDs, which would allow you to make less requests and thus reduce the load on the application.NB: I have a patch ready that implements this behavior, and this will be the basis of an upcoming PR.
Checklist
The text was updated successfully, but these errors were encountered: