-
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
Crash when upgrading from 2.0 to 3.2 #491
Comments
Hi, I'm getting the exact same issue when upgrading 0.1.7 to 0.3.1 or 0.3.2. Works ok on 0.2.x.
|
Thanks @tombuildsstuff . I can confirm the issue is fixed in 3.3! |
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! |
Terraform Version
v0.10.8
Also tested v0.10.6, same issue
Affected Resource(s)
Might be related to storage account?
Terraform Configuration Files
The code is quite long and split across several files and modules. I can upload extracts on demand if required. I'll just paste the container registry code as the crash looks related to it:
Debug Output
I've run with
TF_LOG=debug
but it shows several passwords and access keys. I can upload extracts on demand if required.Panic Output
Expected Behavior
No changes. Infrastructure is up-to-date.
Actual Behavior
!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Steps to Reproduce
terraform plan
is successful with:terraform plan
crashesThe text was updated successfully, but these errors were encountered: