Can't add auth triggers through CLI

[kevinxu3]

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v18.16.0

Amplify CLI Version

12.1.1

What operating system are you using?

Mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Describe the bug

I'm trying to update my auth triggers with existing lambda functions but I get this error from CloudFormation:

Parameters: [functioncircleAuthPreSignupArn, functioncircleAuthPreSignupLambdaExecutionRole, functioncircleAuthPreSignupName, ...{same pattern for other functions}...] must have values

I had issues getting the cli to run perfectly so I manually changed some things in cli-inputs.json.
This is the error when trying to update auth config.

? Which triggers do you want to enable for Cognito Create Auth Challenge, Define Auth Challenge, Pre Sign-up, V
erify Auth Challenge Response
? What functionality do you want to use for Create Auth Challenge Create your own module
? What functionality do you want to use for Define Auth Challenge Create your own module
? What functionality do you want to use for Pre Sign-up Create your own module
? What functionality do you want to use for Verify Auth Challenge Response Create your own module
Error updating the Cognito trigger: The "path" argument must be of type string. Received undefined

Possible related to this (#12784)

Expected behavior

Stack deploys correctly with lambdas set as triggers

Reproduction steps

Create lambdas for auth triggers then add those lambdas through the cli or cli-inputs.json. Deploy and it will fail.

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[ykethan]

Hey @kevinxu3, thank you for reaching out. could you let us know the changes made on the cli-inputs.json file? as this would enable us in reproducing a identical environment.

[ykethan]

additionally noticed that you are looking to add existing Amplify CLI created Lambda functions as a trigger on the Auth resource. unfortunately this is currently not supported by Amplify CLI.
Could you try reverting the changes made on the cli-inputs.json, then run amplify update auth to add the triggers?

[kevinxu3]

Got it. I resolved this by creating new triggers and copying over code. Thanks!

[ykethan]

Glad to hear you are back up and running. Closing the issue, please feel free in reaching out to us again.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please 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.