akshbhu

Discussed offline

Hi @dhruvbansal2 From the error it seems that , if found a construct in userPool groups CFN template with name "`CustomGroup"`. Can you check in auth `cli-inputs.json/parameters.json` if you have...

Hi @Phobarp Can you check the ```userNameConfiguration``` attribute value in your cognito console ? If the value if enabled on that , You can try removing the ```usernameCaseSensitive``` flag from...

Hi @Phobarp Nice to know it worked for you. Have you checked the ```userNameConfiguration``` in your Cognito Console ? I believe your ```UserNameConfiguration``` on cloud might be set to true...

Hi @lovemai073 Thanks for the feature request. Cognito isnt supported in many regions and amplify cli categories depedsn on Cognito.

hi @Wyfy0107 Can you try our enhancement on amplify status command ? For detailed cfn diff you can try : ```amplify status -v ``` Let me know if this is...

Hi @Wyfy0107 We are only showing the diffs for the Root stack for Appsync as this might be the only difference from previous push. I have marked this as Feature...

Hi @agrantdeakin @hico34 It seems like we don't support imported Identity pool sharing in multi envs , as its overriding the BucketName of specific env in the authRole IAM policies...

Hi @petar-prog91 Currently we don't support Custom Identity providers in amplify-cli. The only supported providers are: ```'COGNITO', 'Facebook', 'Google', 'LoginWithAmazon', 'SignInWithApple'``` I can take this a FR to support Custom...

Hi @fpronto Thanks for the feature request 👍 Can you elaborate more on your usecase as it will help us in designing better solutions?