Closed petmongrels closed 4 months ago
changes in avni-server, avni-media, avni-etl
tested with organisation joya@goonj
@petmongrels we have avni-media config in pre-release configured to work with S3 Urls for media content within the bucket "prerelease-user-media". Replacing them with Prod configurations will break convention we have followed across the system configuration and is not a good idea from long term maintenance perspective.
AVNI_MEDIA_S3_BUCKET_NAME: prerelease-user-media AVNI_MEDIA_S3_ZIP_UPLOAD_BUCKET_NAME: prerelease-user-media
For the issue "try to download multiple images through download button it contains empty folder not contains any images" We need to do away with usage of configured AVNI_MEDIA_S3_BUCKET_NAME info, and instead use Media URL specific AVNI_MEDIA_S3_BUCKET_NAME to get this working.
This would then start working, as we give all our AWS_ACCESS_KEYS privileges across all Buckets and their content objects and do not restrict them to a specific env (Prod, prerelease, staging, etc..) Buckets.
Tasks done