Bug: Lambda Layer v14 empty

[willbamford]

Expected Behaviour

v14 Lambda Layer should contain packages.

Current Behaviour

v14 Lambda Layer is empty.

Steps to Reproduce

Calling:

aws lambda get-layer-version-by-arn --arn arn:aws:lambda:us-east-1:094274105915:layer:AWSLambdaPowertoolsTypeScript:14 --region us-east-1

And then downloading the Content.Location results in empty zip:

nodejs
  node_modules
    <nothing-in-here>

Seems broken across regions.

But v13 is populated with packages i.e.

aws lambda get-layer-version-by-arn --arn arn:aws:lambda:us-east-1:094274105915:layer:AWSLambdaPowertoolsTypeScript:13 --region us-east-1

Possible Solution

No response

Powertools for AWS Lambda (TypeScript) version

latest

AWS Lambda function runtime

18.x

Packaging format used

Lambda Layers

Execution logs

No response

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #typescript channel on our Powertools for AWS Lambda Discord: Invite link

[dreamorosi]

Hi @willbamford thank you for reporting this, we'll be taking a look today and report back here.

[am29d]

I can confirm the folder is empty, I am looking into that.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.

[am29d]

Reopened the issue. I will first release a new layer version, once the new deployment confirms, I will close this issue.

[am29d]

Hey @willbamford , thanks again for reporting the bug quickly. The new version 15 is available in all supported regions. And sorry for the issues we might have caused with the empty layer release.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues 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.