aws-amplify / amplify-cli

The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
Apache License 2.0
2.83k stars 823 forks source link

Getting an error following the AWS Amplify Team Environments docs #13808

Closed dwrynngs closed 4 months ago

dwrynngs commented 5 months ago

Amplify CLI Version

12.10.2

Question

I am trying to follow the team environment docs for amplify. I have set up a dev env and then a stg env from the dev env. I have them committed to separate git branches with the same names. They work fine when set up.

I then added a simple storage table to the dev env. A simple dynamodb database using the command 'amplify add storage'. That added correctly. I then followed the example for 'Adding & deploying features in an environment'. I checked out my stg branch, and changed amplify env to stg. I then ran a git merge dev and resolved conflicts on some files (issue with gitignore). I then tried an 'amplify status' command before I tried an 'amplify push'. I got the following error using 'amplify status --debug'

Screenshot 2024-06-06 at 13 04 36

I cannot see what the issue is. I searched for 'mfaConfig..' and only found it in the backend-config.json file. There were not changes to the previous version that worked fine. This is blocking me from using the team environments workflow on amplify. I dont know if I am doing something wrong, or if there is a bug in amplify cli for this workflow.

ykethan commented 5 months ago

Hey @dwrynngs, thank you for reaching from the error >>>> mfaConfig.. , it appears the git merge has left over >>> in the file causing the push to fail. Could you check the amplify/backend/backend-config.json and amplify/backend/backend/cli-inputs.json files for the mfaConfiguration and ensure this does not contain the arrow as provided in the error?

ykethan commented 4 months ago

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue

github-actions[bot] commented 4 months ago

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.