Add Get Endpoint for Image metadata and presigned url

[asuresh-code]

Description

See #37.

Testing instructions

• Review code
• Check Actions build
• Review changes to test coverage

Agile board tracking

closes #37

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 97.43590% with 1 line in your changes missing coverage. Please review.

Project coverage is 98.22%. Comparing base (005e416) to head (43bea90).
Report is 6 commits behind head on develop.

Files with missing lines	Patch %	Lines
object_storage_api/core/exceptions.py	90.90%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop      #69      +/-   ##
===========================================
+ Coverage    98.09%   98.22%   +0.13%     
===========================================
  Files           21       21              
  Lines          368      395      +27     
===========================================
+ Hits           361      388      +27     
  Misses           7        7              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[asuresh-code]

One of the requirements for this issue listed here #37 (comment) , requires that the endpoint:

Must gracefully deal with a situation when the file object with the given object_key doesn't exist

When given an object key that doesn't exist, the presigned url is still generated without any error being thrown. The issue only arises when you open the url and are greeted with this response.

I wanted to check if this would still be a requirement for the back-end to handle or the front-end? S3 won't throw any exceptions when generating the url, so if the check has to be done in the back-end, it would require an additional call to S3 to get the file, implemeting something like this https://stackoverflow.com/questions/33842944/check-if-a-key-exists-in-a-bucket-in-s3-using-boto3

A similar questions was asked here https://stackoverflow.com/questions/78010875/how-to-directly-generate-presigned-url-if-key-exist-in-s3-or-upload-obj-and-cre, and the response was to add an explicit check referenced in my 1st link

[joelvdavies]

One of the requirements for this issue listed here #37 (comment) , requires that the endpoint:

Must gracefully deal with a situation when the file object with the given object_key doesn't exist

When given an object key that doesn't exist, the presigned url is still generated without any error being thrown. The issue only arises when you open the url and are greeted with this response.

I wanted to check if this would still be a requirement for the back-end to handle or the front-end? S3 won't throw any exceptions when generating the url, so if the check has to be done in the back-end, it would require an additional call to S3 to get the file, implemeting something like this https://stackoverflow.com/questions/33842944/check-if-a-key-exists-in-a-bucket-in-s3-using-boto3

A similar questions was asked here https://stackoverflow.com/questions/78010875/how-to-directly-generate-presigned-url-if-key-exist-in-s3-or-upload-obj-and-cre, and the response was to add an explicit check referenced in my 1st link

Yeah this behaviour is fine. I just checked the front end and it displays the right message when it fails to load from the URL so I it's fine to leave the URL in and ignore the check.

[joelvdavies]

Some initial comments, one I am not sure on but we can discuss, worked well on the front end when we tested it.

[joelvdavies]

Just some minor comments and suggestions.

[joelvdavies]

Looks good, final few minor comments. Will get Viktor to have a look over the error handling next week to see what he thinks.

[rowan04]

Minor docstring changes?

[rowan04]

Some more minor docstring changes