[Bug] [Resource] The zombie resources cannot be deleted

[ErikXu]

Search before asking

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

What happened

I uploaded some resources using a user account named test. Then I deleted the user before deleting the resources by mistake. The resources become zombie resources and cannot be deleted even using the open api:

curl -X DELETE "http://www.example.com/dolphinscheduler/resources/90034" -H "Request-Origion:SwaggerBootstrapUi" -H "accept:*/*" -H "Content-Type:application/x-www-form-urlencoded;charset=UTF-8"

The response is:

{
  "code": 10010,
  "msg": "user 60,010 not exists",
  "data": null,
  "failed": true,
  "success": false
}

What you expected to happen

It should be a way to force deleting the zombie resources.

How to reproduce

1. Create a user name test
2. Use test to create directories or upload some files
3. Delete the test user
4. The resources become zombie

Anything else

No response

Version

3.0.0

Are you willing to submit 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

[boy-xiaozhang]

hello,current dolphinscheduler deleting a user does not delete the resource created by the current user, and the user is verified when deleting the resource.

[ErikXu]

Is it possile to provide an api to do a force deletion that did not verify the user?

[github-actions[bot]]

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[bot]]

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.