Maintenance: Skip Layer version checks for the Gamma environment in the Partitioned Layer Publish Workflow

[sdangol]

Summary

We should skip the Layer version check for the Gamma environment during the Partitioned Layer Publishing workflow since it will always fail

Why is this needed?

The layer version checking in the Gamma environment fails during a release because the layers in the Gamma are used for testing and will not be in sync

Which area does this relate to?

Automation

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.