Skip to content

feat: add user agent to default KMS clients - #598

Merged
alex-chew merged 3 commits into
mainlinefrom
add-user-agent
Jul 13, 2022
Merged

alex-chew merged 3 commits into
mainlinefrom
add-user-agent

Conversation

@alex-chew

Copy link
Copy Markdown
Contributor

Description of changes: Adds a AwsEncryptionSdkNet/x.y.z user agent to KMS clients vended by the default client supplier. Adding the user agent to other KMS calls (including in single-key keyrings) is left as later work.

This was tested by running the AWS KMS multi-keyring example and checking that the desired user agent appears in the CloudTrail logs for the corresponding KMS actions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@alex-chew
alex-chew requested a review from a team as a code owner July 12, 2022 21:13

[assembly: AssemblyTitle("AWS.EncryptionSDK")]

// This should be kept in sync with the version number in AWSEncryptionSDK.csproj

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Modern .NET versions allow to generate this assembly metadata automatically (e.g. derive AssemblyVersion from Version), so that we wouldn't need to manually keep these in sync. But so long as we support .NET Framework, AFAICT there isn't an automated mechanism to avoid this duplication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants