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

amplify pull does not fetch Cognito userGroups created from amplify studio #1093

Open
2 tasks done
Eliav2 opened this issue Jan 20, 2024 · 3 comments
Open
2 tasks done
Labels
auth An issue identified as a authentication bug/feature feature-request An issue which is a feature-request created by customer

Comments

@Eliav2
Copy link

Eliav2 commented Jan 20, 2024

How did you install the Amplify CLI?

npm

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

v18.16.1

Amplify CLI Version

12.10.0

What operating system are you using?

windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

only from Amplify studio. not via aws services directly.

Describe the bug

  • created new group in 'User management' tab in amplify studio.
  • amplify pull
  • I would expect to see userPoolGroups resource in my project, however I only have
┌──────────┬─────────────────────────┬───────────┬───────────────────┐
│ Category │ Resource name           │ Operation │ Provider plugin   │
├──────────┼─────────────────────────┼───────────┼───────────────────┤
│ Api      │ medspaceacademy         │ No Change │ awscloudformation │
├──────────┼─────────────────────────┼───────────┼───────────────────┤
│ Auth     │ medspaceacademyc70e7951 │ No Change │ awscloudformation │
├──────────┼─────────────────────────┼───────────┼───────────────────┤
│ Storage  │ medspaceQuestions       │ No Change │ awscloudformation │
└──────────┴─────────────────────────┴───────────┴───────────────────┘

this cognito pull is already hosting some real users. I can't delete it and recreate it using the cli. how do I effectively importing it so my local amplify cli would recognize this user pool?

Expected behavior

.

Reproduction steps

.

Project Identifier

.]

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@Eliav2 Eliav2 added the pending-triage An issue that is pending triage label Jan 20, 2024
@ykethan
Copy link
Member

ykethan commented Jan 22, 2024

Hey @Eliav2, thank you for reaching. we should be able to add the group using Amplify CLI by running amplify update auth and select Create or update Cognito user pool groups which should create a user pool group managed by Amplify CLI. Do remove the user pool group on the Amplify Studio before adding and pushing on AmplifyCLI to prevent any push failures.

@ykethan ykethan added auth An issue identified as a authentication bug/feature pending-response An issue is pending response from the issue requestor labels Jan 22, 2024
@Eliav2
Copy link
Author

Eliav2 commented Jan 23, 2024

Yes i know that deleting the pool from amplify studio and recreating it from cli would work. But i can't delete this pool. Does there is any way to 'pull' or 'import' this pool so amplify cli would recognize it?
After all, i can just create a new user pool directly from amplify studio. If amplify cli can't be aware of user pools created by amplify studio there should be a clear red warning that notify this or just removing this option completely from amplify studio.

@github-actions github-actions bot removed the pending-response An issue is pending response from the issue requestor label Jan 23, 2024
@ykethan
Copy link
Member

ykethan commented Jan 23, 2024

Hey @Eliav2, you should be able to pull the user pool from studio but it appears pulling the user pool groups created on studio is currently not supported.
marking this as feature-request and transferring to amplify studio repository for tracking.

@ykethan ykethan transferred this issue from aws-amplify/amplify-cli Jan 23, 2024
@ykethan ykethan added feature-request An issue which is a feature-request created by customer and removed pending-triage An issue that is pending triage labels Jan 23, 2024
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 feature-request An issue which is a feature-request created by customer
Projects
None yet
Development

No branches or pull requests

2 participants