Configure PROFILE_IMAGE_BACKEND when using AWS s3

[GustavoKatel]

See SE-559

Turns out that to upload profile images to aws, the profile images backend has to be configured similar to the default file storage. This PR adds the ansible variable to the configuration_storage_settings entry in OCIM.

Ref: https://github.com/edx/configuration/blob/master/playbooks/roles/edxapp/defaults/main.yml#L688

Sandbox URL:
Sandbox with the current change in the extra settings: https://gustavo-profile-image-test.stage.opencraft.hosting/

Testing instructions:

1. Set up the Ocim devstack with this branch.
2. Deploy an instance with default configurations and using s3.
3. Create a new AppServer and check on its configurations if EDXAPP_PROFILE_IMAGE_BACKEND is set and matches:

EDXAPP_PROFILE_IMAGE_BACKEND:
  class: storages.backends.s3boto.S3BotoStorage
  options:
    headers:
      Cache-Control: max-age-"{{ EDXAPP_PROFILE_IMAGE_MAX_AGE }}"
    location: '{{ EDXAPP_AWS_LOCATION }}/profile-images'

4. After the provision, set a profile picture for one of its user and check if the url points to aws s3.

Reviewers

• @symbolist

[symbolist]

Can you move this to /mixins/storage.py#S3BucketInstanceMixin? There are a few other related properties there.

[symbolist]

This reference will get out of date so we can leave it out. :)

[symbolist]

Hmm. Since django-storages defaults to the global ones can we get away with not passing the ones which are already set? I think only location and headers are unique here.

[GustavoKatel]

You're right! Thanks for the tip :)

[symbolist]

edX uses 120 as line length so you may want to set that in your IDE and undo these formatting changes.