Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable Unlink Cognito User Pool and Identity Pool for deleted identity pool #464

Closed
3 tasks done
inv-bismillahkhans opened this issue Jan 21, 2022 · 9 comments
Closed
3 tasks done
Labels
auth An issue identified as a authentication bug/feature bug An issue which has been identified as a bug cli An issue that needs to be tracked by CLI team

Comments

@inv-bismillahkhans
Copy link

Before opening, please confirm:

App Id

d1cjnlfryemnao

Region

ap-northeast-1

Environment name

stagging

Amplify CLI Version

No response

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

7.6.5

What operating system are you using?

ubuntu

Browser type?

Google chrome

Describe the bug

I have two amplify application having shared same cognito service . i deleted one amplify application which delete cognito service i am Unable to Unlink Cognito User Pool and Identity Pool for deleted identity pool from my present amplify application.
image
image
[32mEdit your schema at /tmp/amplify-cb0489a2-ac5c-4898-8782-cabfb5587431/amplify/backend/api//schema.graphql or place .graphql files in a directory at /tmp/amplify-cb0489a2-ac5c-4898-8782-cabfb5587431/amplify/backend/api//schema�[39m �[31mFailed to pull the backend.�[39m �[31mThe previously configured Cognito User Pool: '' (ap-northeast-1_IjOP6KWKW) cannot be found.�[39m �[0mError: The previously configured Cognito User Pool: '' (ap-northeast-1_IjOP6KWKW) cannot be found.�[0m �[0m at headlessImport (/opt/amazon/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-auth/src/provider-utils/awscloudformation/import/index.ts:1199:13)�[0m

Expected behavior

It should be unlink the cognito service

Reproduction steps

1.create amplify application with cognito authentication service
2.Create another amplify application using previous cognito service
2.Delete first amplify application with cognito
3. Unllink the cognito from the second amplify application

Additional information

No response

@abhi7cr
Copy link
Contributor

abhi7cr commented Jan 24, 2022

Hi @inv-bismillahkhans,

Thanks for reporting. The current behavior of unlink expects a user pool to exist, else it would throw an error. I will discuss with the team on this particular use-case and get back to you.

@DavidBelkacem
Copy link

I am facing the same issue, did you find a solution ?

@murali-j-99 murali-j-99 added bug An issue which has been identified as a bug auth An issue identified as a authentication bug/feature labels Jul 8, 2022
@reeslabree
Copy link

likewise - can't reconnect a user pool because I can't unlink it, can't unlink it because it's gone

@sanghvian
Copy link

Same @abhi7cr - can you please provide an update on this ?

@ykethan ykethan added pending-triage An issue that is pending triage and removed auth-configure labels Dec 6, 2022
@adilahkb adilahkb removed the pending-triage An issue that is pending triage label Jan 5, 2023
@Ge0rgear
Copy link

Ge0rgear commented Jan 7, 2023

Hello.

The issue persist, does anybody have an update or solution about this incident?

Regards.

@ykethan ykethan added the studio-backend An issue that needs to be tracked by Studio Backend team label Jan 20, 2023
@Newbgen
Copy link

Newbgen commented Jun 13, 2023

Was there ever a solution for this? I am facing a similar issue as well too.

@murali-j-99 murali-j-99 added cli An issue that needs to be tracked by CLI team and removed studio-backend An issue that needs to be tracked by Studio Backend team labels Jul 6, 2023
@ykethan
Copy link
Contributor

ykethan commented Feb 16, 2024

aws-amplify/amplify-cli#13588 (comment)
workaround using Amplify CLI to update the resource

@cwoolum
Copy link
Contributor

cwoolum commented May 15, 2024

Amplify CLI is the recommended approach for making the required updates. I will close this ticket

@cwoolum cwoolum closed this as completed May 15, 2024
Copy link

⚠️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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth An issue identified as a authentication bug/feature bug An issue which has been identified as a bug cli An issue that needs to be tracked by CLI team
Projects
None yet
Development

No branches or pull requests