aws-amplify / aws-amplify/amplify-cli

Add/Edit signin and signout redirect URIs removes lambda trigger

Open
#2,079 4 comments 1 reaction 0 assignees View on GitHub
auth feature-request ops-auth p3
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

**Describe the bug**
When editing the signin and signout url from CLI for social providers, it deletes all stuffs related to lambda trigger for cognito.

**To Reproduce**
Steps to reproduce the behavior:
1. amplify auth add (with social provider)
2. amplify push
3. amplify auth update (add lambda trigger)
4. amplify push
5. amplify auth update
```shell
Please note that certain attributes may not be overwritten if you choose to use defaults settings.

You have configured resources that might depend on this Cognito resource. Updating this Cognito resource could have unintended side effects.

Using service: Cognito, provided by: awscloudformation
What do you want to do? Add/Edit signin and signout redirect URIs
Which redirect signin URIs do you want to edit? http://localhost:3000/
? Update http://localhost:3000/ https://newurl.com/
Do you want to add redirect signin URIs? No
Which redirect signout URIs do you want to edit? http://localhost:3000/
? Update http://localhost:3000/ https://newurl.com/
Do you want to add redirect signout URIs? No
Successfully updated resource projectnamef3085b86 locally

Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud
```

**Expected behavior**
I expect this update to touch nothing else than callbacks url in all config files.

**Desktop (please complete the following information):**
CLI version 1.8.1

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.