Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

nodejs downgraded to v12

See original GitHub issue

What is the problem?

We are upgrading from v1.118.0 to v1.130.0. We noticed as part of the upgrade that some of the implicit lambdas were downgraded from the nodejs 1.14 runtime to the 1.12 runtime. In particular, this is happening for the CertificateRequestorFunction lambda created via aws_certificatemanager.DnsValidatedCertificate, and the framework-onEvent lambda created via custom_resources.Provider.

I don’t know which module is responsible for these lambda runtimes.

Reproduction Steps

Deploy a stack with aws_certificatemanager.DnsValidatedCertificate and custom_resources.Provider using CDK v1.118.0.
Deploy the stack again with CDK v1.130.0 and look at the diff.

What did you expect to happen?

The lambda runtime should have remained at nodejs 14.

What actually happened?

It downgraded to nodejs 12.

CDK CLI Version

1.130.0

Framework Version

No response

Node.js Version

16.13.0

OS

Alpine 3.14

Language

Python

Language Version

3.9

Other information

No response

Issue Analytics

State:
Created 2 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

peterwoodworthcommented, Oct 10, 2022

You aren’t linking to the latest code @gkumar7. It uses v14, we don’t use v12 anymore in any of our functions https://github.com/aws/aws-cdk/blob/0f002e2009bbab2e10c08cdf908c5091ba61b754/packages/%40aws-cdk/aws-certificatemanager/lib/dns-validated-certificate.ts#L110

0reactions

gkumar7commented, Oct 10, 2022

Stumbled on this issue as I see the latest cdk version is still using NodeJS 12.x. With NodeJS v12.x EOL, could we at least add a parameterized way to update DnsValidatedCertificate to use NodeJS 14.x?