I am creating a new amplify environment.
amplify push is failing with error : "Resource Name: UserPoolClientLambda (AWS::Lambda::Function) Resource handler returned message: "The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs18.x) while creating or updating functions. (Service: Lambda, Status Code: 400, Request ID: 0f1026f5-a173-45a4-b143-65d60d89f684)" (RequestToken: 99495106-e2dc-19d5-ae88-11f11945bdec, HandlerErrorCode: InvalidRequest)".
I upgraded to amplify CLI version 12.10.0 but still having this issue. How do I tell Amplify to use later version of nodejs? Any other settings that control this in Amplify? Please help.
What options do I have to fix this?
Thanks.
#UserPoolClientLambda nodejs12.x is no longer supported
distant quest
obsidian lintel
@distant quest you may need to run amplify update auth and run through the flow then push which should upgrade the NodeJS version. you may need to migrate your resource if prompted by the CLI.
distant quest
Thanks. I was able to push with 'amplify update auth'. But now the generated graphql queries are not nested anymore. Only 'getxxxx' queries are nested. List and index queries are not nested. How do fix it. We still use V1 graphql transformation. e.g.
' @key(
name: "ByCompany"
fields: ["companyId", "firstname", "lastname", "createdAt"]
queryField: "providerByCompany"
)'
The the generated providerByCompany graphql query does not have nested types anymore. I have tried maxdepth as 2.
We were on amplify cli 10.5.1 with v1 transformer. We upgraded to latest version of cli keeping v1 transformer. The graphql queries generated were not the same as we had with cli 10.5.1. What steps should we take to ensure the generated qraphql queries are the same as with 10.5.1 ? Please advise.