aws-amplify / aws-amplify/amplify-cli

Custom auth provider and custom auth domain got removed with an amplify auth update to change cognito triggers

Open
#6,715 1 comment 1 reaction 1 assignee Claimed by @josefaidt View on GitHub
auth feature-request ops-auth p4
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

**Is your feature request related to a problem? Please describe.**
So you want a custom domain for your auth resouce? Great
You also want to add another Auth Provider, like you own SSO portal running Keycloak? Great!

But then you also want to enable/disable/change some Cognito Lambda triggers. You run `amplify update auth` and suddenly everything is gone again. :( No longer is your custom domain added or your custom OpenID provider!

**Describe the solution you'd like**
The ability to not have everything get blow away when you want to update your Cognito Lambda triggers. Add a custom OpenID option for auth providers. Add a custom domain option for the auth resource.

**Describe alternatives you've considered**
- Manually adding everything back in!
- Running a script to update the `parameters.json` file used for setting up the Cognito Auth resource before running `amplify push`.

**Additional context**
https://github.com/aws-amplify/amplify-cli/issues/6701
https://github.com/aws-amplify/amplify-cli/issues/1880
https://github.com/aws-amplify/amplify-cli/pull/6499/files

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.