-
Notifications
You must be signed in to change notification settings - Fork 826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot update Nodejs runtime version of UserPoolClientLambda function #13726
Comments
Hey @eagren20, Could you run |
|
Glad to hear that @eagren20. Closing the issue, feel free in reaching out to us if you have any issues. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
In my particular case I had to upgrade the amplify CLI to: 12.13.0. Also had to adjust the amplify build settings to nodejs version 18 (I previously had 16). @ykethan - is there a list of supported nodejs versions supported by Amplify Console for building? |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.13.2
Amplify CLI Version
12.11.1
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Manually changed runtime versions of custom lambda functions to 18
Describe the bug
I cannot complete an amplify push because the Nodejs runtime version of the function UserPoolClientLambda is 14, which is no longer supported. As this is an auto generated function there doesn't appear to be a way to manually update the runtime version in the cloudformation files. I am using the latest version of the CLI.
Expected behavior
Successful amplify push
Reproduction steps
This project was created several years ago when nodejs runtime 14 was still used so there is no reliable way to recreate it
Project Identifier
353214476f258ac72d41a4057d9c5ae7
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: