-
Notifications
You must be signed in to change notification settings - Fork 50
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
bugfix: ImdsCredentialsProvider: Avoid double slashes in URLs #1380
bugfix: ImdsCredentialsProvider: Avoid double slashes in URLs #1380
Conversation
Affected ArtifactsChanged in size
|
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.
Looks great, thanks for the bug fix!
{ | ||
"id": "5a460540-14ee-4d26-a860-8cd122323b34", | ||
"type": "bugfix", | ||
"description": "ImdsCredentialsProvider: Avoid double slashes in URLs" |
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.
Nit: Thank you for creating a changelog entry. Please follow the guidelines in the CONTRIBUTING.md doc for description
, specifically around use of imperative present tense. For example: "Stop using double slashes in `ImdsCredentialsProvider` URLs"
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.
Thank you, updated.
b6da68e
to
70397ee
Compare
|
Alright this change is merged and should be available in tomorrow's release. |
Great to hear. Thank you for helping move it along, @ianbotsf! |
Description of changes
The fix to #1303 introduced a change where the
CREDENTIALS_BASE_PATH
constant was updated with a trailing slash. Existing usage of this constant to construct longer paths did not take this into account, leading to double slashes at the concatenation point. Unfortunately,ImdsCredentialsProviderTest
did not assert request matches on its interactions, so this was not caught at the time of change. Change the usage of the base path constant and add request match assertions to hopefully catch new regressions.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.