Updating an amplify Auth implementation

Which Category is your question related to?

Auth

Amplify CLI Version 3.12

Provide additional details e.g. code snippets

Using the CLI is great to get started, but incredibly difficult (in my opinion) to make changes.

I have a working Signup, Sign-In, Forgotten Password etc… process which also uses a Lambda trigger to add a user to a group… I would like to add an additional “Post Confirmation” trigger, but I can’t seem to do this without impacting existing settings.

When I …

amplify update auth

it is very difficult to walk through the existing settings without making changes… I simply want to add a new “custom” Lambda trigger, but I’m diffing the existing files and seeing multiple changes such as:

`

• “authSelections”: “identityPoolAndUserPool”,

• “authSelections”: “userPoolOnly”, `

At this point, I have backed out of the change, reverted all files and regretted starting this project with amplify.

How do I make a simple update like adding a new Lambda PostConfirmation module?

[pantareh]

@danhumphrey Yes. I just realized that. thanks! I still don’t understand why this approach is chosen over file editing. With file editing you can diff and track changes. It’s weird that that CLI is now practically becoming a chat UI with all these questions 😃

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.