search

CS4850Group5A / VirtuDoc

1 stars 3 forks source link

Fixed malformed S3 configuration #267

Closed ARMmaster17 closed 2 years ago

ARMmaster17 commented 2 years ago

Summary

The AWS 3rd party library was set up to automatically configure the region to use for file storage. When I originally set this up, the documentation led me to believe that it could perform some kind of lookup with the AWS API to find the region for our assigned bucket. What actually happens is that if auto: true is set, it tries to guess the region from where the app is currently running. Since Heroku containers run on AWS in us-east-1. it was attempting to use that region to talk to our S3 buckets, which are in us-west-2. This PR overrides that change.

Closes #265

How to Test

Unfortunately, as this is a DevOps-related issue, this can only be tested in production. Once this PR is merged and deployed, you can attempt to create a file by creating an appointment.

PR checks below will perform regression testing to ensure that existing configuration did not break, but it is impossible to test the production profile until it is deployed.

github-actions[bot] commented 2 years ago

Unit Test Results

15 files  ±0  15 suites  ±0   28s :stopwatch: ±0s 84 tests ±0  84 :heavy_check_mark: ±0  0 :zzz: ±0  0 :x: ±0 

Results for commit c7173d2a. ± Comparison against base commit cd698492.