Minio Integration for the Profile Pictures Storage Backend

[tetnaylin]

Description 🧾

• Added the backend implementation for the profile picture storage using the minio object store.
• The implementation should verify whether the base64 encoding that is passed in is valid and should remove the old image when a new image or an empty string is passed in.
• A new filename should be created for every new upload to minimise the likelihood of different files having the same file names.

Testing

• Using an API client, we first send a get request via the guest login route. Then the following were tested using the session cookie:
  • Successfully uploading a valid base64 encoding profile picture and storing the profile picture url in the database.
  • Error cases for images that are not of MIME type jpg, jpeg or png.
  • Successful removal of the old profile picture when a new profile picture is passed in.
  • Successful removal of the user's current profile picture when an empty string is passed in.
• Another get request via the guest login route is then sent to obtain a different session cookie. Then the following were tested using the new session cookie:
  • Similar behaviour without affecting any of the other profile pictures uploaded by other users.

Checklist

• 📍 You have assigned yourself to this pull request.
• 🔗 You have linked an issue to which this pull request closes.
• 💭 Leave any relevant specific directions to reviewers.
• 👀 No secrets in clear text in the pull request.
• 🎟️ To categorise release notes, the pull request should be labelled with at least one of these labels:
  • feature: for application feature improvement or new features
  • bug: fixing something that previously wasn't working
  • dev: development-side related changes
  • docker: updates to the Docker code
  • setup: changes to the setup/infrastructure of the codebase
  • test: updates to internal testing