Search before asking

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

Description

Purpose:
A user-friendly and high-performance restful API is our goal.

Refactor reason:

• Use restful style to unify API specifications
• Solve the current incomplete API document and reduce the threshold of API use
• Improve API reusability
• Reduce unnecessary data return and improve performance
• Improve the readability of the code and reduce the maintenance cost
• Improve the accuracy of error reporting

API output Standard:

1. Content-Type using application/json(segmented upload file is not applicable)
2. Users can simply understand how to call the API normally by reading the API docs
3. The input and output parameters of API should avoid using types that cannot be intuitively understood, such as JSON and MAP
4. All enumeration values in the API need to be included in the API document
5. Comply with restful specifications
6. The error information requested by API can accurately express the cause of the error
7. Rename all process to workflow as we discussed in [DSIP-7] [API] Suggest refactor the backend api #10257 (comment)
8. The service refactoring part and the controller refactoring part should be divided into two PR base on the conclusions in [Feature-10983] [refactor] ResourcesController #10998 (comment)

Please reply the controller name and its function name you want to participate in and the issue you created. I will link it to this issue and assign it to you. Anyone who wants to participate is very welcome ^_^

Current API

Login page

Project manage page

Project

Workflow Monitor

Workflow Relationship

Workflow Definition

Workflow Instance

Task Definition

Task Instance

Task Group

Mornitor center

Datasource center

Resource center

Dataquality center

Security center

Scheduler

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

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