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

Parameters: [auth#appname#IdentityPoolId] do not exist in the template #13797

Closed
2 tasks done
PeterSchoell opened this issue May 14, 2024 · 6 comments
Closed
2 tasks done
Labels
auth Issues tied to the auth category of the CLI pending-triage Issue is pending triage

Comments

@PeterSchoell
Copy link

How did you install the Amplify CLI?

npm

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

v21.5.0

Amplify CLI Version

12.12.0

What operating system are you using?

Microsoft Windows 10 Business

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

No manual changes made.

Describe the bug

When attempting to update the auth category of a project the deployment fails with the following error.

🛑 The following resources failed to deploy:
Resource Name: authuserPoolGroups (AWS::CloudFormation::Stack)
Event Type: update
Reason: Parameters: [auth#appname#IdentityPoolId] do not exist in the template

Expected behavior

The auth category changes can be deployed

Reproduction steps

Have an Amplify project with auth category

Make some change to the auth

Run amplify push -y.

Project Identifier

No response

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.
@PeterSchoell PeterSchoell added the pending-triage Issue is pending triage label May 14, 2024
@AnilMaktala
Copy link
Member

Hi @PeterSchoell  👋,  thanks for raising this issue.we are working on reproducing the issue. Could you please run below command and send us the project identifier amplify diagnose --send-report.
please refer here

@AnilMaktala AnilMaktala added pending-response Issue is pending response from the issue author api-graphql Issues related to GraphQL resources in the API category labels May 14, 2024
@PeterSchoell
Copy link
Author

amplify diagnose --send-report

Project Identifier: 1665dd35b4fc64548f5cf355f7fb1828

Thank you very much for the quick reply!

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label May 14, 2024
@AnilMaktala
Copy link
Member

Hi @PeterSchoell, Thank you for providing the diagnose report. I'm going to transfer this over to our CLI repository for better assistance.

@AnilMaktala AnilMaktala added the transferred This issue was transferred from another Amplify project label May 24, 2024
@AnilMaktala AnilMaktala transferred this issue from aws-amplify/amplify-category-api May 24, 2024
@ykethan
Copy link
Member

ykethan commented May 29, 2024

Hey @PeterSchoell, Could you provide us some additional information on the update made on the auth resource such as prompts selected and inputs provided. This would assist in reproducing the issue.
Could you check the backend-config.json and amplify-meta.json, if the userPoolGroups contains the dependsOn block with IdentityPoolId?

@ykethan ykethan added auth Issues tied to the auth category of the CLI pending-response Issue is pending response from the issue author and removed api-graphql Issues related to GraphQL resources in the API category transferred This issue was transferred from another Amplify project labels May 29, 2024
@PeterSchoell
Copy link
Author

I have redone many settings, rebuilt and pushed some things. The result was that everything worked again at some point. Unfortunately, I cannot provide any further details. The problem must have taken me two weeks.

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Jun 4, 2024
Copy link

github-actions bot commented Jun 4, 2024

This issue is now closed. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth Issues tied to the auth category of the CLI pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

3 participants