-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Terraform Crash #200
Comments
Stack trace:
|
Hey @brettaukburg Thanks for reporting this issue - I've taken a look into this and opened PR #204 with a fix. Thanks! |
Checking the HTTP Response isn't `nil`. Fixes #200
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
This issue was originally opened by @brettaukburg as hashicorp/terraform#15646. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
In the gist
Terraform Configuration Files
Debug Output
Panic Output
https://gist.github.com/brettaukburg/7ef24d9d8ff70b58bc42c9708e640944
Expected Behavior
I expected the "terraform destroy -parallelism=200" to remove all the resources that I had built with Terraform.
Actual Behavior
Terraform panics instead of executing any of the destroy.
Steps to Reproduce
Important Factoids
Running in Azure
The subscription had a limit of 800 VMs which stopped the original apply
References
none
The text was updated successfully, but these errors were encountered: