Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Implement Bulk Cancel Analyses #2153

Open
Shevijacobson opened this issue Nov 3, 2024 · 3 comments
Open

Implement Bulk Cancel Analyses #2153

Shevijacobson opened this issue Nov 3, 2024 · 3 comments
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Shevijacobson
Copy link
Contributor

Shevijacobson commented Nov 3, 2024 •
edited by mguetta1
Loading

Description:
Currently, the bulk cancellation of analyses is achieved by sending a separate request to the server for each selected application. This approach results in multiple network calls, which could impact performance and scalability.

To improve efficiency, we should implement a bulk cancellation feature that allows all selected analyses to be canceled with a single server request. This change would make the functionality similar to the existing bulk deletion process for applications.

Suggested Solution:

  • Update the backend API to support a bulk cancellation endpoint that can process multiple application IDs in a single request.
  • Modify the frontend to use this new endpoint, ensuring all selected analyses are canceled simultaneously with one request.

Benefits:

  • Reduces server load by consolidating multiple cancellation requests into a single operation.
  • Improves user experience with faster and more efficient bulk operations.

Reference:
Related Pull Request: #2099
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels Nov 3, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Nov 3, 2024
This was referenced Dec 8, 2024
Merged
Merged
jortel pushed a commit to konveyor/tackle2-hub that referenced this issue Jan 17, 2025
@MiriSafra
✨ Add bulk cancel functionality for analyses (#769)
55d5e94 
Added a function for cancelling multiple analyses at once.
Resolves: [tackle2-ui issue #2153](
konveyor/tackle2-ui#2153)

Signed-off-by: MiriSafra <[email protected]>
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Planning Jan 17, 2025
@mguetta1
Copy link
Collaborator

mguetta1 commented Jan 18, 2025 •
edited
Loading

Related Hub work:

@mguetta1 mguetta1 reopened this Jan 18, 2025
@mguetta1
Copy link
Collaborator

Related UI work:

mguetta1 pushed a commit that referenced this issue Jan 22, 2025
@MiriSafra
✨ Implement bulk analysis cancellation (#2163)
501c787 
Update the backend to implement a bulk cancellation functionality,
enabling the cancellation of multiple analyses based on provided IDs in
a single request. Modify the existing logic to integrate the new
endpoint for handling multiple cancellations simultaneously.

Part of: #2153 

---------

Signed-off-by: MiriSafra <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Planning
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mguetta1 @Shevijacobson