Maintenance: Update InvokeStore to v0.2.1

[svozza]

Summary

The InvokeStore package release a new version (v.0.2.1) last week that didn't export types correctly for a particular tsconfig.json setup. This affected Powertools so we didn't not upgrade. Yesterday a new version was released that fix the issue.

Why is this needed?

v0.2.x contains important changes to the API that we need to account for:

// old
import InvokeStore from '@aws/lambda-invoke-store';

// new
import InvokeStore from '@aws/lambda-invoke-store';

 //.. 
export const handler = () => {
  const invokeStore = InvokeStore.getInstanceAsync();
}

Which area does this relate to?

Other

Solution

We must upgrade to the new version and rather than using InvokeStore directly from the import, we must use globalThis.awslambda.InvokeStore.

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.29.0 version!