[Improvement][dolphinscheduler-api] A dependent node cannot depend on the workflow it is in

[Mrhs121]

Search before asking

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

Description

In the current version, users are allowed to depend on the workflow itself when updating a workflow that contains dependent nodes(For example, the dep_ods_dwd workflow in the following figure).
This causes two problems:

• ont is circular dependency
• the other is that once the workflow containing the dependent node is successfully created, it cannot be deleted due to the circular dependency.

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

[Mrhs121]

https://dolphinscheduler.apache.org/zh-cn/docs/3.3.2/guide/task/dependent

Regarding this example "Weekly Report A also needs to execute successfully by itself last Tuesday", I have a question :
After test_dag_A is created successfully, at this time the conditions in depend node only include b and c, and then I modify test_dag_A again. In the depend node, a new condition was added that requires A to execute successfully last Tuesday.
Finally, after saving, execute test_dag_A. Suppose tasks B or C were executed successfully last week, but test_dag_A had never been executed before. So at this point, condition "a in depend node that was executed successfully last Tuesday" will never be satisfied, and test_dag_A will remain blocked forever. Am I right in my analysis?

@SbloodyS cc

[SbloodyS]

@Mrhs121 Yes, you're right.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.