Skip to content
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.

Sign up for GitHub

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

Jump to bottom

File at path: 'C:\Users\Pavel\Desktop\Code_PB\2024\wl2412\amplify\#current-cloud-backend\amplify-meta.json' does not exist #13505

Closed
2 tasks done
pborokh opened this issue Dec 25, 2023 · 3 comments
Closed
2 tasks done

File at path: 'C:\Users\Pavel\Desktop\Code_PB\2024\wl2412\amplify\#current-cloud-backend\amplify-meta.json' does not exist #13505

pborokh opened this issue Dec 25, 2023 · 3 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-init Issues related to initializing a new Amplify project

Comments

@pborokh
Copy link

pborokh commented Dec 25, 2023

How did you install the Amplify CLI?

npm

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

20.10.0

Amplify CLI Version

12.10.0

What operating system are you using?

windows

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

Deleted backend using Amplify Studio

Describe the bug

amplify push results with an error
🛑 File at path: 'C:\Users\Pavel\Desktop\Code_PB\2024\wl2412\amplify#current-cloud-backend\amplify-meta.json' does not exist
Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from:
'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 32bdce88-972b-4d80-9c3f-8ac116bed63b

Expected behavior

app's backend deployed in dev environment

Reproduction steps

Running a react fullstack tutorial, after the first deployment delete the backend and try reinstating it from CLI using Amplify Push

Project Identifier

44e8f24d4a27ca069ca01eb0b1f9ec66

Log output

# Put your logs below this line

Additional information

No response

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.
@pborokh pborokh added the pending-triage Issue is pending triage label Dec 25, 2023
@ykethan
Copy link
Member

ykethan commented Dec 27, 2023

Hey @pborokh, thank you for reaching out. If the backend environment was deleted in the AWS Amplify console , to create a new env with the same resources, we should be able to remove the team-provider-info.json file and run amplify init creating a new env with a different name.

@ykethan ykethan added pending-response Issue is pending response from the issue author platform-init Issues related to initializing a new Amplify project labels Dec 27, 2023
@josefaidt
Copy link
Contributor

Closing due to inactivity

@josefaidt josefaidt closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 2, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-init Issues related to initializing a new Amplify project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@josefaidt @pborokh @ykethan