-
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
Panic using 1.16.0 provider #2089
Comments
Also affects 1.15.0 as well. If I downgrade to 1.14.0, everything works fine. |
Hi @simongh, I'm sorry to hear your having this issue. Could I trouble you to share the panic's full stack trace/log output? And if possible the terraform causing it. the part i am interested in looks something like this:
thanks! |
I've got a very massive crash log. The best I can see is :
I'm not sure how useful this is, but this is the bit where it panics. The relevant HCL is, I think:
|
hmmm. This specific block seems to cause problems. If I comment it out, no panic. Re-enable it panic. It seems related to the variables it's using, since other environments use this same block (it's in a module) without problem.
Even more specifically, changing the requested_service_objective_name to a fixed value stops the panic |
I've tracked it down the |
Hi @simongh, Thank you for the effort in tracking down the cause! I have added validation to the property so it can no longer be empty in #2125 However it is strange, the crash log is:
showing a crash on accessing the |
@simongh taking a look at the Terraform Configuration posted above - just a heads up that from Terraform 0.12+ you'll need to ensure the resource names/ID's are quoted (this syntax is supported in older versions of Terraform too) 🙂 e.g.
needs to become
|
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 👉 [email protected]. Thanks! |
Community Note
Terraform Version
terraform 0.11.8
azurerm provider 1.16.0
Affected Resource(s)
Running terraform plan causes a panic. I'm limited in what I can share, as our infosec would have kittens, but I can share parts of the file if it'll help. It appears to be related to a network security rule.
Terraform Configuration Files
Debug Output
Panic Output
panic: runtime error: invalid memory address or nil pointer dereference
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: