[Improvement] [API] Resource center API Optimization

[EricPyZhou]

Search before asking

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

Description

This optimization will be applied to the resource center API and is also part of the OSPP event. At the end of the event, the resource center API will mostly depend on the third-party API. relations about tasks and resources will be the only information stored in t_ds_resources.

Future work on refactoring will be considered upon completion of this issue.

Use case

No response

Related issues

Resource center optimization

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

[github-actions[bot]]

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting

[zhongjiajie]

does we will totally remove table t_ds_resource in the end?

[EricPyZhou]

does we will totally remove table t_ds_resource in the end?

In the end, yes. But for now, we will keep it for backward compatibility. A new table t_ds_relation_resources_task is dedicated to storing resources used by tasks in online workflows.