PROFILE_IMAGE_BACKEND settings disappeared after v16.0.4

[dyudyunov]

The PROFILE_IMAGE_BACKEND settings were present from the v14 to v16.0.4 (latest before v17).

Here is the PR where it was added and the merge commit from it.

But they are absent starting from v17 and now I can reproduce the issue from the mentioned PR (an uploaded profile picture disappears after the redeploy because it is stored locally).

I checked the repo several times but don't know what I'm missing here. What happened? Why did the setting disappear?

Notes:

• without updated PROFILE_IMAGE_BACKEND settings profile images will be stored locally and lost after the next deployment on k8s installations.
• I tested it with redwood.2 release (tutor v18.1.3, minio v18.0.0)

[DawoudSheraz]

Hi. The setting was removed when upgrading to quince to fix an issue with profile photos. It seems some items might still be needed.

• feat: Upgrade to Quince #31
• [LEARNER] <LMS: PROFILE> Upload photo openedx/wg-build-test-release#333

[dyudyunov]

Just for history - here is my working profile image backend config:

PROFILE_IMAGE_BACKEND = {
    "class": DEFAULT_FILE_STORAGE,  # "storages.backends.s3boto3.S3Boto3Storage"
    "options": {
        # The bucket name value corresponds to default value of {{ MINIO_BUCKET_NAME }} - the only public bucket
        # https://github.com/overhangio/tutor-minio/blob/master/tutorminio/templates/minio/tasks/minio/init.sh#L6C31-L6C48 AFAIK
        "bucket_name": "openedx",  
        "querystring_auth": False,
        "location": PROFILE_IMAGE_BACKEND["options"]["location"].lstrip("/"),
    },
}

I was unable to use the private bucket + querystring_auth because of the SignatureDoesNotMatch error.

As I understood from the shallow investigation - querystring_auth doesn't work because _get_profile_image_urls appends additional querystring kwarg &v=.... If you remove it from the URL - signature works as expected.