You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting custom user age metadata via an aws.customMetadata.* system property, the expected values do not show up in requests's User-Agent header. Different metadata set via the aws.frameworkMetadata property do properly show up so this seems to be unique to custom metadata.
Expected behavior
Custom metadata set via aws.customMetadata.*are included in the User-Agent header.
Current behavior
Custom metadata set via aws.customMetadata.*are not included in the User-Agent header.
Steps to Reproduce
Configure DEBUG-level logging and run the following code:
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
When setting custom user age metadata via an
aws.customMetadata.*
system property, the expected values do not show up in requests'sUser-Agent
header. Different metadata set via theaws.frameworkMetadata
property do properly show up so this seems to be unique to custom metadata.Expected behavior
Custom metadata set via
aws.customMetadata.*
are included in theUser-Agent
header.Current behavior
Custom metadata set via
aws.customMetadata.*
are not included in theUser-Agent
header.Steps to Reproduce
Configure DEBUG-level logging and run the following code:
View the DEBUG output and inspect the request headers. The
User-Agent
string contains other metadata but not the custom metadatafoo=bar
.Possible Solution
No response
Context
No response
AWS Kotlin SDK version used
0.17.6-SNAPSHOT
Platform (JVM/JS/Native)
OpenJDK Runtime Environment Corretto-17.0.4.8.1 (build 17.0.4+8-LTS)
Operating System and version
Amazon Linux 2
The text was updated successfully, but these errors were encountered: