ignore content_type from credentials provider #106
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Yes!
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Default metadata credentials provider in yandex cloud environment (http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/token) returns access token in json format, but with text/plain content type.
This is wrong, but code from
iam.auth.MetadataUrlCredentials._make_token_request()
ignores content type and everything works fine in sync implementation.On the other hand, its async alternative
aio.iam.MetadataUrlCredentials._make_token_request()
fails with wrong content type error.Issue Number: N/A
What is the new behavior?
Now we ignore content type from metadata credentials provider. This is also wrong, but acceptable, since sync implementation also do this.
Other information