error saying parameter.json does not exist in auth folder #13716
Labels
pending-response
Issue is pending response from the issue author
pending-triage
Issue is pending triage
platform-pull
Issues related to `amplify pull`
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
20
Amplify CLI Version
12.10.3
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.
yes since I was unable to run amplify pull after i manually added the auth folder from the s3 deployment bucket into the directory manually after running amplify pull but before finishing local configurations.
Describe the bug
Originally when I pull the project from git and ran amplify pull i would get an error like this
2022-11-14T06:16:50.802Z [WARNING]: ✖ There was an error initializing your environment. 2022-11-14T06:16:50.816Z [INFO]: 🛑 Failed to pull the backend. 2022-11-14T06:16:50.816Z [INFO]: File at path: amplify/backend/auth/xxxxxxxxxxxxxxxxxxx/parameters.json' does not exist
After deleting amplify folder and config files and running amplify pull app iid --- env name --
get this error
🛑 Failed to pull the backend.
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: xxxxxxxxxxxxxxxxx
im able to pull the backend if I amplify pull --app id and manually add the auth folder from the s3 deployment bucket into the amplify directory manually after running amplify pull but before finishing local configurations.
Other notes:
Expected behavior
run amplify pull and backend should update
Reproduction steps
Project Identifier
Project Identifier: 9aca2a984adc2c198809949dbc7c5b96
Session Identifier: 34977174-b7e9-43f2-9086-fab981582108
Log output
Additional information
im able to pull the backend if I amplify pull --app id and manually add the auth folder from the s3 deployment bucket into the amplify directory manually after running amplify pull but before finishing local configurations.
Other notes:
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: