They all reference AWS.Logger.Core and use the AWSLoggerCore(AWSLoggerConfig config, string logType) constructor from this package to instantiate the CloudWatch client. Each logging provider passes a different string for the logType parameter of the constructor which is then passed on to the UA string. The logType parameter is only used in the UA string and no where else.
This PR updates the value passed to the logType parameter such that it also includes the assembly version for each logging provider.
The final UA string that get appended to the CloudWatch client is as follows: (assembly versions are based on the version bumps performed in this PR).
Issue #, if available: SDK-169882
Description of changes: chore: Update User-Agent string
We have 4 separate projects in this repo each serving as a different type of logging provider.
They all reference AWS.Logger.Core and use the
AWSLoggerCore(AWSLoggerConfig config, string logType)constructor from this package to instantiate the CloudWatch client. Each logging provider passes a different string for thelogTypeparameter of the constructor which is then passed on to the UA string. ThelogTypeparameter is only used in the UA string and no where else.This PR updates the value passed to the
logTypeparameter such that it also includes the assembly version for each logging provider.The final UA string that get appended to the CloudWatch client is as follows: (assembly versions are based on the version bumps performed in this PR).
lib/aws-logger-core#3.3.1.0 ft/aws-logger-aspnetcore#3.5.1.0lib/aws-logger-core#3.3.1.0 ft/aws-logger-nlog#3.3.1.0lib/aws-logger-core#3.3.1.0 ft/aws-logger-log4net#3.5.1.0lib/aws-logger-core#3.3.1.0 ft/aws-logger-serilog#3.4.1.0I have used the
ft/prefix for this because customers can independently use the AWS.Logger.Core package to pass their own logging provider as well.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.