You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the api category has the status of No Change) the deployment fails with the following error.
Parameters: [unauthRoleName] do not exist in the template
Expected behavior
The auth category changes can be deployed, even if there has been no change to the api category.
Reproduction steps
Have an Amplify project with an api and auth category, where all changes have been deployed and both categories have the status No 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 the unauthRoleName error when trying to deploy the api category.
Project Identifier
No response
Log output
# Put your logs below this line
UPDATE_IN_PROGRESS apiPROJECTNAME AWS::CloudFormation::Stack Mon Apr 29 2024 08:17:27 GMT+0000 (Coordinated Universal Time)
UPDATE_FAILED apiPROJECTNAME AWS::CloudFormation::Stack Mon Apr 29 2024 08:17:28 GMT+0000 (Coordinated Universal Time) Parameters: [unauthRoleName] do not exist in the template
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 status Update, and then amplify push will successfully complete for both.
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.
The text was updated successfully, but these errors were encountered:
alice-was-here
changed the title
Parameters: [unauthRoleName] do not exist in the template
Parameters: [unauthRoleName] do not exist in the template
Apr 29, 2024
Hey @alice-was-here, thank you for the information. On diving into the files noticed the parameters.json under the api/<api-name>/build folder contains the following
"authRoleName": {
"Ref": "AuthRoleName"
},
but the parameters.json at the api/<api-name> root folder does not contain this.
Transferring the issue to our API repository for better assistance.
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: