feat: Delete requests to API don't respond with a valid JSON response

[bryan-aguilar]

Is this a new feature, an enhancement, or a change to existing functionality?

Enhancement

How would you describe the priority of this feature request

Low (would be nice)

Please provide a clear description of problem this feature solves

Not all requests to /delete/ routes respond with valid JSON bodies. This causes a little bit of user pain when trying to make requests directly through the carbide rest api and parse the response. Currently the /delete/ routes I have utilized return with a plain string.

Feature Description

1. From a user perspective I want all requests to the carbide api to return valid json.

Describe your ideal solution

No response

Describe any alternatives you have considered

No response

Additional context

No response

Code of Conduct

• I agree to follow NCX Infra Controller's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request

[thossain-nv]

@bryan-aguilar In REST API, deletions are typically responded with HTTP 202 Accepted (if deletion is carried out async) or HTTP 204 No Content where deletion is carried out immediately.

For HTTP 204 No Content where the object is removed immediately does not allow returning any response body.

Our REST API handlers that return HTTP 202 Accepted currently includes a text string - we can update that to return a JSON response instead.

Would that satisfy as a solution?