GSoC 2025 Qualification Task: Integrate New Single-Call DID Listing in Rucio WebUI

[maany]

Description

The Rucio Server now provides a new endpoint, GET /dids/{scope}/dids/list, which returns a stream of NDJSON objects representing fully populated DIDs. Currently, the ListDID feature in the Rucio WebUI leverages a post processing pipeline that requires multiple calls (one initial stream followed by individual GET DID calls) to gather complete details.

Objectives

Create a New Gateway Endpoint

Implement a new Gateway endpoint in the WebUI that calls the Rucio Server’s new endpoint (GET /dids/{scope}/dids/list).

Update the ListDID Use Case

Convert the existing ListDID use case from a BaseSingleEndpointPostProcessingPipelineStreamingUseCase to a BaseSingleEndpointStreamingUseCase so that it makes a single call to the server.

Ensure Frontend Integration

Update the WebUI component that displays DID details to utilize the new single-call approach.

Testing and Validation

Add or update tests to verify that

• The new Gateway endpoint correctly interfaces with the backend.
• The updated ListDID use case processes and displays data as expected.
• The overall performance improves by reducing the number of API calls.

Evaluation Criteria

1. A new Gateway endpoint in the WebUI calls the new Rucio Server endpoint.
2. The ListDID use case is refactored to use BaseSingleEndpointStreamingUseCase.
3. The WebUI correctly displays fully populated DID data using the new single call.
4. Appropriate tests are in place, and all tests pass.
5. The code adheres to the project's contribution guidelines.
6. The issue is referenced and assigned to the corresponding Pull Request.

Useful Resources

https://rucio.github.io/documentation/developer/webui/webui_frontend_vscode_dev_env

[ahmedbilal008]

Hi, I'd like to work on this issue as a GSoC 2025 candidate. Could you please assign this task to me? Thanks!

[maany]

Hi, I'd like to work on this issue as a GSoC 2025 candidate. Could you please assign this task to me? Thanks!

Hi @ahmedbilal008, please reach out to Martin and I over email and I can share a detailed set of instructions with you :) The emails are listed in the Mentor section of the GSoC Project Description

[Sahi1l-Kumar]

@maany Instead of using this new endpoint GET /dids/{scope}/dids/list , we can also use GET /dids/{scope}/dids/search endpoint which is currently being used and just make the name parameter optional in the frontend and backend like shown in image.

This approach improves application performance by initially retrieving only the names of the DIDs in a single request. Users can then fetch detailed information for a specific DID on demand by clicking on it, reducing unnecessary data transfer and improving responsiveness. What are your thoughts?