Maintenance: concatenate Powertools for AWS UA to existing `AWS_SDK_UA_APP_ID`

[dreamorosi]

Summary

Customer can set a AWS_SDK_UA_APP_ID environment variable in their AWS Lambda config.

When this happens, the customer’s value should preserved and our UA string should be appended.

For example, if customer has set the variable in their Lambda config, we’d see APP/CUSTOMER_STRING_FROM_LAMBDA_CONFIG/PT/NO-OP/Version.

Why is this needed?

So that we can continue appending our user agent to AWS SDK client requests even when customers set their own app id.

Which area does this relate to?

No response

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v2.25.2 version!