Description of problem:

The DELETE API request in tackle2-hub works in such a way that it does not check if the resource exists before deleting it.

From a user perspective, I expect the behavior to be consistent across all HTTP methods, and get a 404 status with an error message: "record not found" if the resource doesn't exist, same as the GET method

Version-Release number of selected component (if applicable):

Upstream

Attachments

screenshot_delete_204.png
screenshot_get_404.png