Feature request: `identity` field should be unknown in AppSync Event types

[dreamorosi]

Use case

Customers on the AWS Community Builders Slack have reported that the null type used for the identity field in the types of the new AppSync Events solver are too strict.

This is correct, because the field can have different content based on the authorization method used.

Solution/User Experience

As per title, mark the field as unknown in the types and explain in the docstring.

Alternative solutions

Acknowledgment

• This feature 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.

[github-actions]

⚠️ COMMENT VISIBILITY 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 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.

[github-actions]

This is now released under v2.20.0 version!