OpenViking DELETE /api/v1/fs returns 500 Internal Server Error for resources that are still being asynchronously processed (isDir status not yet resolved), even when the delete actually succeeds server-side.

• Return a proper error code (e.g., 409 Conflict) when the resource is in a transient state

TL;DR

Implement a check for the asynchronous processing status before returning a response for the DELETE /api/v1/fs request to handle resources that are still being processed.

Guidance

• Verify the current implementation of the DELETE /api/v1/fs endpoint to understand how it handles asynchronous processing of resources.
• Consider introducing a mechanism to check the status of the resource being deleted, such as polling or using a callback, to ensure it is not in a transient state.
• Evaluate the feasibility of returning a 409 Conflict error when the resource is in an asynchronous processing state, as an alternative to the current 500 Internal Server Error.
• Review the wait=False parameter in the POST /api/v1/resources request to determine if it can be leveraged to wait for the asynchronous processing to complete before attempting to delete the resource.

Example

No code example is provided due to the lack of specific implementation details in the issue description.

Notes

The provided workaround of waiting for async processing to complete before deleting may not be suitable for all use cases, and a more robust solution should be explored.

Recommendation

Apply a workaround by waiting for async processing to complete before deleting resources, as this approach is explicitly mentioned in the issue and can provide a temporary solution until a more permanent fix is implemented.