-
Notifications
You must be signed in to change notification settings - Fork 41
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 connector automatic endpoint discovery #1370
Conversation
There were 2 bugs. 1. We modified only req.URL{Scheme, Host} with the new endpoint, we missed req.Host. 2. We were modifying the endpoint after signing the request. 2 did not show up until 1 was resolved. This is likely because the request signing doesn't take req.URL{Scheme, Host} into account.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, thanks for fixing this!
Approved, but just wanted to double-check whether this would be considered a user-facing bug and would therefore warrant a CHANGLOG entry?
@diverdane Thanks, CHANGELOG entry added |
f46e95e
to
b54d2d9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Code Climate has analyzed commit b54d2d9 and detected 1 issue on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 53.0% (0.0% change). View more on Code Climate. |
@doodlesbykumbi this may be out of scope for this PR, but I think I saw you mention a mock AWS server that we might be able to use for AWS integration tests. should we file an issue in this project to implement that? it would have been nice to have some integration tests for this connector. |
What does this PR do?
What's changed? Why were these changes made?
There were 2 bugs.
2 did not show up until 1 was resolved. This is likely because the request signing doesn't
take req.URL{Scheme, Host} into account.
How should the reviewer approach this PR, especially if manual tests are required?
N/A
Are there relevant screenshots you can add to the PR description?
N/A.
What ticket does this PR close?
Resolves #1369
Checklists
Change log
Test coverage
Documentation
README
s) were updated in this PR, and/or there is a follow-on issue to update docs(For releases only) Manual tests