File service download metadata end point issue
Scenario: User hits File service GET metadata signed API with an Invalid Id (Say opendes:file:21107053-17bf-405e-9dd3-bb0a1e9b8e0aTEST).
Sample Request URL: https://os-file-attcrcktoa-uc.a.run.app/v1/files/opendes:file:21107053-17bf-405e-9dd3-bb0a1e9b8e0aTEST/metadata
Expected:- { "error": { "code": 404, "message": "Record Not Found", "errors": [ { "domain": "global", "reason": "notFound", "message": "Record Not Found" } ] } }
Actual:- { "error": { "code": 500, "message": "Failed to find record for the given file id.", "errors": [ { "domain": "global", "reason": "internalError", "message": "Failed to find record for the given file id." } ] } }