Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: aws server endpoint configuration handling #1971

Merged
merged 5 commits into from
Oct 31, 2018
Merged

fix: aws server endpoint configuration handling #1971

merged 5 commits into from
Oct 31, 2018

Conversation

allanlw
Copy link

@allanlw allanlw commented Oct 30, 2018

This fixes bug #1966 by correctly handling the AWS_SERVER environment variable that is outlined in the .env.example

I tested this manually in the following cases:

  • S3 configuration with AWS_SERVER unset
  • S3 configuration with AWS_SERVER set to the empty string
  • S3 configuration with AWS_SERVER explicitly set to the S3 endpoint for my bucket's region
  • Google Cloud Storage with AWS_SERVER set to storage.googleapis.com

In all four cases, uploading and viewing avatars works as expected, so I think it's unlikely that this will cause any breakage.

In the default case (where AWS_SERVER is unset and/or empty)
set the value of the endpoint to null. Note that the underlying
S3Client ignores args in the parameter array that are null,
because it calls 'isset' on them.
@CLAassistant
Copy link

CLAassistant commented Oct 30, 2018

CLA assistant check
All committers have signed the CLA.

@asbiin
Copy link
Member

asbiin commented Oct 30, 2018

Nice work, thank you for your help @allanlw ! I had removed the 'endpoint' value, because I though it was useless, but it wasn't ...

@asbiin asbiin merged commit 1ce2bcb into monicahq:master Oct 31, 2018
@allanlw allanlw deleted the fix-aws-server branch November 4, 2018 16:39
@github-actions
Copy link

This pull request has been automatically locked since there
has not been any recent activity after it was closed.
Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants