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.

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

amplify env remove test, removed all resources of prod branch #12954

Closed
Weixuanf opened this issue Jul 17, 2023 · 3 comments
Closed

amplify env remove test, removed all resources of prod branch #12954

Weixuanf opened this issue Jul 17, 2023 · 3 comments
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question

Comments

@Weixuanf
Copy link

Amplify CLI Version

can't remember (cuz I upgraded afterwards), but it wasn't the latest version

Question

I had my main amplify env branch prod, which includes all the resources (dynamo db tables, s3 buckets, cognito, ...)
then I did amplify env add another branch called test. I think I added it when I try to do amplify push on it, it throws exception: 🛑 Template error: instance of Fn::GetAtt references undefined resource authokband411e4d5b
which made me unable to finish amplify push (so I think no resources (dynamo tables, s3 buckets, ...) was generated for test branch

so i decided to just remove this branch by amplify env remove test, then to my shock, it remove ALL my resources (dynamo db tables, s3 buckets, cognito, ...) in prod branch....maybe it's because the amplify push for test branch was never finish so it didn't link its own resources but instead linked prod's resources??

But anyway it resulted in a tragedy that the test branch and all my resources of prod branch was removed. prod branch was left with an empty branch with no resources.

I don't know if I did something wrong that resulted this

@Weixuanf Weixuanf added pending-triage Issue is pending triage question General question labels Jul 17, 2023
@josefaidt
Copy link
Contributor

Hey @Weixuanf 👋 thanks for raising this! While we begin to look at this in more depth would you mind posting the project ID output from amplify diagnose --send-report?

@josefaidt josefaidt added the pending-response Issue is pending response from the issue author label Jul 17, 2023
@josefaidt
Copy link
Contributor

Closing due to inactivity

@josefaidt josefaidt closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2023
@github-actions
Copy link

⚠️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
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage question General question
Projects
None yet
Development

No branches or pull requests

2 participants