Maintenance: Prevent error when AWS_LAMBDA_FUNCTION_NAME is not passed in the Idempotency Persistence Layer

[sdangol]

Summary

The part where we set the idempotencyKeyPrefix now throws an error if the environment variable AWS_LAMBDA_FUNCTION_NAME is not present in the execution environment.

Previously, this passing this variable was optional and it would not throw an error.

Why is this needed?

This could break the testing workflow who are are not passing that environment variable.

Which area does this relate to?

Idempotency

Solution

Pass '' as a defaultValue to the getStringFromEnv function in https://github.com/aws-powertools/powertools-lambda-typescript/pull/4314/files#diff-9ec12bfb8fddec824e9c5a12714d42f23135cabae6e7e3fa6ea9e58a90440498R40-R43

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.