-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Improvement][API] API operation optimization #6772
Comments
Hi:
|
Good job! I thinks this is a huge change, and we should add label |
Can you add the background explanation of why to do that? |
Sometime we only need to create workflow without schedule, do you think we should support it or not? I thinks the schedule just an additions informations to workflow, mean that url would look like
should we also add downstream for tasks? Oh, I see that in
why should we delete downstream tasks? |
It create a empty offline workeflow. I think one dag should have schedule.
You're right, here we can support add/delete downstream tasks |
|
I'll complete the releaseTaskDefinition interface! |
I will implement interface "createEmptyProcessDefinition" and "updateProcessDefinitionBasicInfo" |
I'll complete the “deleteProcessDefinitionVersion”(num 5) |
fix swagger view at #6933 |
收到。
|
Search before asking
Description
Dag API
Task API
Relation API
Execution API
Use case
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: