Is it possible to delete all data scopes in a connection with few clicks on UI?

[Stepness]

Currently Id like to delete a connection, but Im blocked because I have to delete all associated data scopes first.

Is there a button to delete them all in one go? Because I can't find it
I saw in previous discussion that an implementation to delete single scopes has been done in #5558

[dosubot[bot]]

Hey @Stepness! I'm here to assist you with any bugs, questions, or contributions while you wait for a human maintainer. Let's tackle this together!

Yes, there is existing functionality to support bulk deletion of data scopes in the UI for Apache DevLake. The code includes a rowSelection property in the Table component, which allows for the selection of multiple data scopes. The selected data scopes can then be deleted using the handleDeleteDataScope function.

Here is a relevant code snippet:

<Table
  rowKey="id"
  size="middle"
  loading={!ready}
  columns={[
    // ... other columns
  ]}
  dataSource={dataSource}
  pagination={{
    current: page,
    pageSize,
    total,
    onChange: setPage,
    onShowSizeChange: (_, size) => {
      setPage(1);
      setPageSize(size);
    },
  }}
  rowSelection={{
    selectedRowKeys: scopeIds,
    onChange: (selectedRowKeys) => setScopeIds(selectedRowKeys as ID[]),
  }}
/>

The rowSelection property enables the selection of multiple rows, and the scopeIds state variable keeps track of the selected data scopes ^[1].

If you don't see this option in your UI, it might be worth checking if you are on the latest version of Apache DevLake or if there are any specific permissions required to access this feature.

To continue talking to Dosu, mention @dosu.

[klesh]

Not that I know of. All scope configs of the connection must be deleted one by one first.
Maybe you could write a script to delete them in one go.

[Stepness]

It looks very impractical. Can this feature become a To do?

[klesh]

I am not sure, it is a rare and risky operation, and it is hard to say if it should be available on the UI.
@Startrekzky What do you think?

[Startrekzky]

I also think it's a risky operation.