-
Notifications
You must be signed in to change notification settings - Fork 76
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: [unauthRoleName] do not exist in the template #2512
Comments
Parameters: [unauthRoleName] do not exist in the template
Hey @alice-was-here, thank you for reaching out. Could you provide us the following information.
|
|
Hey @alice-was-here, thank you for the information. On diving into the files noticed the
but the |
Hey @alice-was-here, Are you still experiencing this issue or blocked by this issue? |
Hey 👋 , This issue is being closed due to inactivity. If you are still experiencing the same problem and need further assistance, please feel free to leave a comment. This will enable us to reopen the issue and provide you with the necessary support. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v18.20.2
Amplify CLI Version
12.4.0
What operating system are you using?
Ubuntu (22.04.4)
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 (when theapi
category has the status ofNo Change
) the deployment fails with the following error.Expected behavior
The
auth
category changes can be deployed, even if there has been no change to theapi
category.Reproduction steps
Have an Amplify project with an
api
andauth
category, where all changes have been deployed and both categories have the statusNo Change
Make some change to the
auth
config (I upgraded a lambda in the cloud formation template to run node 18 - but any change will trigger this).Run
amplify push -y
.The cli will successfully begin deploying the
auth
changes. It will throw theunauthRoleName
error when trying to deploy theapi
category.Project Identifier
No response
Log output
Additional information
The changes will successfully deploy IF there is any change to the
api
category resources. So, adding an arbitrary change to the api configuration will cause both categories to be in the statusUpdate
, and thenamplify push
will successfully complete for both.Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: