Skip to content

user agent is not actually being modified #25

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

Closed
mattsb42-aws opened this issue Nov 7, 2017 · 1 comment
Closed

user agent is not actually being modified #25

mattsb42-aws opened this issue Nov 7, 2017 · 1 comment
Assignees
Labels

Comments

@mattsb42-aws
Copy link
Member

Problem

I could have sworn I checked this, but apparently the user agent modification we are doing is not actually taking effect.

Solution

It looks like this needs to be modified on the botocore level, not on the boto3 client level. Unfortunately, this means that we cannot modify the user agent if a user provides a custom KMS client, as we should not be modifying a botocore client that might be used for something else.

In KMSMasterKeyProvider we can modify the botocore client if we build it directly. However, we should not modify a botocore client that was provided to us.

TODO

Make sure that there is not a way to modify the user agent at the boto3 client layer.

@mattsb42-aws mattsb42-aws self-assigned this Nov 7, 2017
@mattsb42-aws
Copy link
Member Author

As part of this, I think we should be copying the botocore session provided rather than using it directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant