Parameters: [unauthRoleName, authRoleName] must have values on `amplify push function` #9484

MichaelPlan · 2022-01-10T21:36:03Z

Before opening, please confirm:

I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
I have searched for duplicate or closed issues.
I have read the guide for submitting bug reports.
I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?

npm

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

v14.18.2

Amplify CLI Version

7.6.7

What operating system are you using?

Mac

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

No manual changes made

Amplify Categories

function

Amplify Commands

add, push

Describe the bug

It's not possible to push a new lambda function with CLI.

UPDATE_FAILED api AWS::CloudFormation::Stack Mon Jan 10 2022 22:32:05 GMT+0100 (Central European Standard Time) Parameters: [unauthRoleName, authRoleName] must have values
CREATE_FAILED functiontest AWS::CloudFormation::Stack Mon Jan 10 2022 22:32:06 GMT+0100 (Central European Standard Time) Resource creation cancelled
UPDATE_FAILED AuthTriggerCustomLambdaStack AWS::CloudFormation::Stack Mon Jan 10 2022 22:32:06 GMT+0100 (Central European Standard Time) Resource update cancelled

Expected behavior

UPDATE_COMPLETE

Reproduction steps

amplify add function
choose Lambda function
function name => test
runtime => NodeJS
function Template => Hello world
advanced settings => No
amplify push function test
" Function │ test │ Create │ awscloudformation"
continue => Y
[unauthRoleName, authRoleName] must have values

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information

No response

The text was updated successfully, but these errors were encountered:

mkpratt · 2022-01-11T19:42:07Z

I also have been dealing with this exact same issue. Fails with this same error on a few existing and unchanged REST APIs when trying to push a minor update on the GraphQL API
Parameters: [authRoleName, unauthRoleName] must have values

Amplify CLI Version 7.6.8

josefaidt · 2022-01-11T21:43:48Z

Hey @MichaelPlan 👋 thanks for raising this! From the CloudFormation lines you posted I noticed this is failing for your API, is this a REST API by chance?

UPDATE_FAILED api AWS::CloudFormation::Stack Mon Jan 10 2022 22:32:05 GMT+0100 (Central European Standard Time) Parameters: [unauthRoleName, authRoleName] must have values

If so, was this project recently migrated from using an older version of the CLI?

MichaelPlan · 2022-01-18T16:47:35Z

@josefaidt yes, the project was recently migrated. The only solution to fix it was to create a complete new project. But after some days working with the new version, I'm now getting this for hours:

A deployment is in progress.
If the prior rollback was aborted, run:
"amplify push --iterative-rollback" to rollback the prior deployment
"amplify push --force" to re-deploy

when try to push anything.

I pulled everything again and made some small changes, but nothing works anymore.
With "amplify push --iterative-rollback" I 'm getting ": ["Index: 1 State: {"preRollback":"previousDeploymentReadyCheck"} Message: Resource is not in the state stackUpdateComplete"]":

In amplify studio I can see "Deployment completed".

Do you have any solution for the problem? Is it possible to abort a deployment?

johnpc · 2022-01-18T20:16:58Z

Did you previously override cloudformation configuration directly?

josefaidt · 2022-02-01T17:19:17Z

Hey @MichaelPlan 👋 to mitigate the parameters issue we should be able to safely remove those parameters, though ideally this should have been done for us. For the deployment issue, if you visit the CloudFormation console do you see a deployment in progress by chance?

josefaidt · 2022-02-15T22:51:26Z

Closing due to inactivity. @MichaelPlan if you are still experiencing this issue please reply back to this thread and we can re-open to investigate further 🙂

LucasKnudsen · 2022-02-23T07:38:39Z

Hey, I'm having similar issues.

I am on version 7.6.21 and migrated to Transformer v2.

amplify push work fine, but amplify function push and amplify function push locationGeocoder throws the following error:

UPDATE_FAILED      apicondominium                       AWS::CloudFormation::Stack Wed Feb 23 2022 08:26:08 GMT+0100 (Central European Standard Time) Parameters: [unauthRoleName, authRoleName] must have values

This is from a newly redeployed Stack as well.

The only place I'm using these values as parameters is within the Geo resource, which was generated by Amplify.

josefaidt · 2022-03-02T21:43:27Z

Hey @LucasKnudsen apologies for the delay! I was able to successfully reproduce this with the following steps on the latest version of the Amplify CLI (7.6.22):

create a new project with amplify init -y
add a GraphQL API with amplify add api, choose IAM as an auth mode
a. in my reproduction, I chose Cognito as the default auth mode and IAM as an additional auth mode
push with amplify push -y
add a function with amplify add function
attempt to push just the new function with amplify push function <my-function-name> or amplify push function
observe error

Marking as a bug 🙂

OlgaMaslova · 2022-06-02T14:34:54Z

Hello,

I am experiencing the same bug when trying to push only function. I have the latest version of amplify (8.3.1). Any ideas?

Thanks!

mstoyanovv · 2022-06-10T12:20:52Z

Hello,

I am experiencing the same bug when trying to push only function. I have the latest version of amplify (8.3.1). Any ideas?

Thanks!

It happens to me too but in my case I recreated the table that was linked to a given function. After that amplify function push started throwing those errors. Relinking the function to the table by amplify function update might solve it.

MaximeIJ · 2022-08-28T05:13:09Z

Same, seeing this in CI/CD builds of a custom function. The logs say they patched the CLI to v 9.2.1:
Done patching NPM package '@aws-amplify/cli' to version 9.2.1

I'm not seeing the issue from local amplify push though

Edit 2 days later: the issue disappeared for me as mysteriously as it appeared.

miquelvir · 2022-08-30T18:09:15Z

Seeing the issue as well.

jbreemhaar · 2022-09-01T14:18:20Z

@edwardfoyle yes, I'm at 9.2.1.

javabudd · 2022-09-03T20:14:00Z

seeing the issue as well, amplify push leads to an error in both the UI and CLI (9.2.1):

AWS::CloudFormation::Stack Sat Sep 03 2022 14:04:58 GMT-0600 (Mountain Daylight Time) Parameters: [unauthRoleName] must have values

bordernone · 2022-09-10T16:40:03Z

Had a similar issue. Here's my solution https://stackoverflow.com/a/73673509/11135757

avinashrgudipati · 2022-09-19T18:19:50Z

Had a similar issue. Here's my solution https://stackoverflow.com/a/73673509/11135757

It was a nightmare but I did the above and didn’t help me. On CI/CD it specifically says unAuthUserRole issue but on the react app it now says Resource not in StackUpdateComplete. Previously the above was followed by unAuthRole error

bordernone · 2022-09-20T14:53:56Z

Had a similar issue. Here's my solution https://stackoverflow.com/a/73673509/11135757

It was a nightmare but I did the above and didn’t help me. On CI/CD it specifically says unAuthUserRole issue but on the react app it now says Resource not in StackUpdateComplete. Previously the above was followed by unAuthRole error

Check if you see the identity pool linked in your "Authentication" section in Amplify Studio. Additionally, you can add StackUpdateComplete to your auth profile.

avinashrgudipati · 2022-09-20T15:10:23Z

@bordernone

I have a cognitive userpool linked. Any idea how I can add the stackUpdateComplete to the auth profile. Thank you for the response

bordernone · 2022-09-20T15:13:56Z

@bordernone

I have a cognitive userpool linked. Any idea how I can add the stackUpdateComplete to the auth profile. Thank you for the response

My question is does it show that you have an identity pool attached as well? This was the reason I was getting the error. I also had user pool linked but no identity pool was linked to it

avinashrgudipati · 2022-09-20T15:17:58Z

Sorry about that. I do not have any identity pool attached. Any steps to attach that would be really appreciated

bordernone · 2022-09-20T15:27:30Z

Sorry about that. I do not have any identity pool attached. Any steps to attach that would be really appreciated

It's actually in that StackOverflow answer I linked above. I will update the answer with more details.

avinashrgudipati · 2022-09-22T18:00:21Z

Any update on this? Stuck and I can’t delete any db items from client because I can’t update API

@bordernone did you have a lambda function in your setup?

bordernone · 2022-09-25T18:31:31Z

Any update on this? Stuck and I can’t delete any db items from client because I can’t update API

@bordernone did you have a lambda function in your setup?

This might help: https://docs.aws.amazon.com/cognito/latest/developerguide/amazon-cognito-integrating-user-pools-with-identity-pools.html

Nope I didn't

avinashrgudipati · 2022-09-25T18:40:11Z

Any update on this? Stuck and I can’t delete any db items from client because I can’t update API
@bordernone did you have a lambda function in your setup?

This might help: https://docs.aws.amazon.com/cognito/latest/developerguide/amazon-cognito-integrating-user-pools-with-identity-pools.html

Nope I didn't

That might be the difference. The issue started happening when I added the function as the OP reported. I will try creating a completely new project without lambda function and try migrating the database

But will try your suggestion again. Thank you kindly for the link @bordernone

javabudd · 2022-10-02T20:31:15Z

experiencing the same bug when attempting to push a new environment importing a cognito user pool...

Deployment failed.
Deploying root stack gtart [ =============--------------------------- ] 1/3
        amplify-gtart-staging-142557   AWS::CloudFormation::Stack     UPDATE_ROLLBACK_COMPLETE       Sun Oct 02 2022 14:28:59…
        apigtart                       AWS::CloudFormation::Stack     CREATE_FAILED                  Sun Oct 02 2022 14:28:30…
Deployed api gtart [ ======================================== ] 12/12

🛑 The following resources failed to deploy:
🛑 An error occurred during the push operation: /
Resource is not in the state stackUpdateComplete

Parameters: [unauthRoleName] must have values

avinashrgudipati · 2022-10-02T20:45:06Z

I don’t want to jinx my self but I got past this. Unfortunately the solution isn’t pretty.

@javabudd how did you create auth?

javabudd · 2022-10-02T21:55:33Z

I don’t want to jinx my self but I got past this. Unfortunately the solution isn’t pretty.

@javabudd how did you create auth?

I used the UI to attach an existing user pool, if I remove the auth and try again it works.

lazpavel · 2022-11-23T17:42:19Z

No longer reproducible with v.10.5.1. PR fix: #10848

Abhishek-cmd13 · 2023-01-07T16:24:29Z

This issue is not been solved yet.

Arnav7501 · 2023-02-05T05:21:41Z

issue is still there

Arnav7501 · 2023-02-05T05:31:43Z

@javabudd how did you remove the auth?

avinashrgudipati · 2023-02-06T06:38:13Z

Removing the auth and re-adding didn’t really help me. The best bet for you and probably the easy one is to create a new environment. I initially deleted my project and started from scratch but later needed to add another function and that broke my environment again. I tried creating a new environment this time which was much easier rather than redoing the whole thing and that worked.

…

On Sun, Feb 5, 2023 at 11:01 AM Arnav Chowdhry ***@***.***> wrote: @javabudd <https://github.com/javabudd> how did you remove the auth? — Reply to this email directly, view it on GitHub <#9484 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2M7IEM4VRV5LYC747AVLJDWV43MZANCNFSM5LUWRGSA> . You are receiving this because you commented.Message ID: ***@***.***>

Arnav7501 · 2023-02-06T06:46:46Z

yeah you're right a new environment fixed it... unfortunately my app is in production and the new environment doesn't keep the logins so that is an extremely unfortunate bug. I appreciate your help though.

josefaidt · 2023-02-14T17:38:51Z

Hey folks 👋 if you are experiencing this error when attempting to push updates to your Amplify project using the latest version of the CLI (10.7.2 at the time of writing), please file a separate bug report

kuoaid · 2024-11-04T23:26:26Z

same issue on Amplify push (all). Using the latest CLI.

josefaidt added the pending-triage Issue is pending triage label Jan 11, 2022

josefaidt self-assigned this Jan 11, 2022

josefaidt added the pending-response Issue is pending response from the issue author label Jan 11, 2022

josefaidt closed this as completed Feb 15, 2022

josefaidt reopened this Mar 2, 2022

josefaidt removed their assignment Mar 2, 2022

josefaidt changed the title ~~Parameters: [unauthRoleName, authRoleName] must have values~~ Parameters: [unauthRoleName, authRoleName] must have values on amplify push function Mar 2, 2022

InnovateWithEric added the p1 label Mar 3, 2022

InnovateWithEric assigned akshbhu Mar 14, 2022

akshbhu mentioned this issue Mar 21, 2022

fix: deploy only function when doing amplify push function #10035

Merged

5 tasks

josefaidt linked a pull request Apr 5, 2022 that will close this issue

fix: deploy only function when doing amplify push function #10035

Merged

5 tasks

johnpc closed this as completed in #10035 Apr 7, 2022

lazpavel closed this as completed Nov 23, 2022

This was referenced Mar 28, 2023

Auth deployments failing via amplify push auth but succeeding via amplify push #12324

Open

amplify push function also pushes GraphQL API, fails if GraphQL has IAM #12348

Open

neuquen mentioned this issue Dec 8, 2023

Amplify Push: Parameters must have values for environment variables #13467

Closed

2 tasks

Parameters: [unauthRoleName, authRoleName] must have values on amplify push function #9484

Parameters: [unauthRoleName, authRoleName] must have values on amplify push function #9484

Comments

MichaelPlan commented Jan 10, 2022

Before opening, please confirm:

How did you install the Amplify CLI?

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

Amplify CLI Version

What operating system are you using?

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

Amplify Categories

Amplify Commands

Describe the bug

Expected behavior

Reproduction steps

GraphQL schema(s)

Log output

Additional information

mkpratt commented Jan 11, 2022 • edited Loading

josefaidt commented Jan 11, 2022

MichaelPlan commented Jan 18, 2022

johnpc commented Jan 18, 2022

josefaidt commented Feb 1, 2022

josefaidt commented Feb 15, 2022

LucasKnudsen commented Feb 23, 2022

josefaidt commented Mar 2, 2022

OlgaMaslova commented Jun 2, 2022

mstoyanovv commented Jun 10, 2022

MaximeIJ commented Aug 28, 2022 • edited Loading

miquelvir commented Aug 30, 2022

jbreemhaar commented Sep 1, 2022

javabudd commented Sep 3, 2022 • edited Loading

bordernone commented Sep 10, 2022

avinashrgudipati commented Sep 19, 2022

bordernone commented Sep 20, 2022

avinashrgudipati commented Sep 20, 2022

bordernone commented Sep 20, 2022

avinashrgudipati commented Sep 20, 2022

bordernone commented Sep 20, 2022

avinashrgudipati commented Sep 22, 2022

bordernone commented Sep 25, 2022

avinashrgudipati commented Sep 25, 2022 • edited Loading

javabudd commented Oct 2, 2022

avinashrgudipati commented Oct 2, 2022

javabudd commented Oct 2, 2022

lazpavel commented Nov 23, 2022 • edited Loading

Abhishek-cmd13 commented Jan 7, 2023

Arnav7501 commented Feb 5, 2023

Arnav7501 commented Feb 5, 2023

avinashrgudipati commented Feb 6, 2023 via email

Arnav7501 commented Feb 6, 2023

josefaidt commented Feb 14, 2023

kuoaid commented Nov 4, 2024

Parameters: [unauthRoleName, authRoleName] must have values on `amplify push function` #9484

Parameters: [unauthRoleName, authRoleName] must have values on `amplify push function` #9484

mkpratt commented Jan 11, 2022 •

edited

Loading

MaximeIJ commented Aug 28, 2022 •

edited

Loading

javabudd commented Sep 3, 2022 •

edited

Loading

avinashrgudipati commented Sep 25, 2022 •

edited

Loading

lazpavel commented Nov 23, 2022 •

edited

Loading