[Feature][Connection configuration] Can we get option to bulk delete / cleanup connection data for connection

[veetmoradiya3628]

Search before asking

• [x] I had searched in the issues and found no similar feature requirement.

Use case

I am looking for bulk option to delete / clear data scope for connection similar to associate scope config we have in the each connection top, it will be help in case when user have more no. of scopes configured and if they want to do operations on more no. of scopes.

Description

i am facing redundant UI click operations since i have more no. of scopes configured in particular connection and my use case is similar to described above.

Related issues

No response

Are you willing to submit a PR?

• [x] Yes I am willing to submit a PR!

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[klesh]

Are you working on it? if so, would you share your plan and/or solution to the problem? Thanks.

[veetmoradiya3628]

Hi @klesh

Yes I'm working on it, going through code and structure, i have below 2 designs in mind.

1. One way: They pick the connections they want gone, then hit a "delete" button. A little window pops up showing how each one is doing as it gets deleted. Thing I'm wondering about: If one of them fails to delete, should I just ignore it and keep going? Also, if something else is happening (like a pipeline running), we can't let them delete anything. What's the best way to tell them that?

2. Another way: The user picks the connections, and then we tell the system to delete them all in one go. Thing I'm wondering about here: If deleting a lot of connections takes a while, the system might time out. How do we stop that from happening? Also, if some of the chosen connections don't get deleted, how do we let the user know which ones?

can you please provide your input which and how to go about it.

[klesh]

Hi @klesh

Yes I'm working on it, going through code and structure, i have below 2 designs in mind.

1. One way: They pick the connections they want gone, then hit a "delete" button. A little window pops up showing how each one is doing as it gets deleted. Thing I'm wondering about: If one of them fails to delete, should I just ignore it and keep going? Also, if something else is happening (like a pipeline running), we can't let them delete anything. What's the best way to tell them that?

"should I just ignore it and keep going?" - How about offering a checkbox for people to choose what they prefer. " if something else is happening (like a pipeline running), we can't let them delete anything. What's the best way to tell them that?" I think an error message about what happened and asking them to try again later is necessary and sufficient.

2. Another way: The user picks the connections, and then we tell the system to delete them all in one go. Thing I'm wondering about here: If deleting a lot of connections takes a while, the system might time out. How do we stop that from happening? Also, if some of the chosen connections don't get deleted, how do we let the user know which ones?

Good points, too many to consider. I think the first way is better, plus, it can be implemented purely in the frontend interactively.

can you please provide your input which and how to go about it.

[github-actions[bot]]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.