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

Verify host when default and custom credentials are used. #4858

Merged
merged 1 commit into from
Mar 17, 2020

Conversation

martinmr
Copy link
Contributor

@martinmr martinmr commented Feb 27, 2020

Currently, the host is only checked when the default credentials are
used. This means using custom credentials will not work if there's no
host in the destination URI as the logic that handles this case is not
executed.

This PR changes the logic so that these checks are always executed,
regardless of the status of the credentials.

Fixes #4855


This change is Reviewable

Currently, the host is only checked when the default credentials are
used. This means using custom credentials will not work if there's no
host in the destination URI as the logic that handles this case is not
executed.

This PR changes the logic so that these checks are always executed,
regardless of the status of the credentials.
@martinmr martinmr requested review from manishrjain and a team as code owners February 27, 2020 00:20
Copy link
Contributor

@manishrjain manishrjain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 2 of 2 files at r1.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved

@martinmr martinmr merged commit be867fa into master Mar 17, 2020
@martinmr martinmr deleted the martinmr/set-host-s3 branch March 17, 2020 16:47
martinmr added a commit that referenced this pull request Mar 17, 2020
Currently, the host is only checked when the default credentials are
used. This means using custom credentials will not work if there's no
host in the destination URI as the logic that handles this case is not
executed.

This PR changes the logic so that these checks are always executed,
regardless of the status of the credentials.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Binary Backups - AWS temporary credentials don't work
2 participants