Maintenance: deprecate AlbMultiValueHeadersSchema in favor of AlbSchema for Parser

[dreamorosi]

Summary

The AlbSchema & AlbMultiValueHeadersSchema are basically the same except for the latter extending the first by adding two properties. These two properties are mutually exclusive with the single-value version of headers and queryStringParameters and their presence depends on how the ALB is configured.

Because of this, we can deprecate the AlbMultiValueHeadersSchema, move the two properties within the AlbSchema and mark all four as .optional().

Why is this needed?

So that we can reduce the amount of built-in schemas customers have to choose from.

Which area does this relate to?

Parser

Solution

Mark the AlbMultiValueHeadersSchema as deprecated and move the two extended properties in the base AlbSchema.

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.

[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.13.1 version!