You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with the terraform plugin framework, defining an attribute with MapNestedAttributes that contains more than one computed attribute crashes terraform before a plan/apply. I couldn't find any mention of the panic message (panic: value is not an object) anywhere in the issues before. The stacktrace points here in go-cty.
I saw this happening in my provider, but I can also reproduce it with the hashicups starter template. I've attached the relevant minimal reproduction code below.
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
When working with the terraform plugin framework, defining an attribute with
MapNestedAttributes
that contains more than one computed attribute crashes terraform before a plan/apply. I couldn't find any mention of the panic message (panic: value is not an object
) anywhere in the issues before. The stacktrace points here in go-cty.I saw this happening in my provider, but I can also reproduce it with the hashicups starter template. I've attached the relevant minimal reproduction code below.
Terraform Version
Terraform Configuration Files
Implementation:
Config:
The crash happens when the "items" are present in the config, but the actual content doesn't matter.
Debug Output
Crash Output
https://gist.github.com/avinashbot/b1ce31f9cfb0501b8f349135a6bb9bda
Expected Behavior
Terraform doesn't crash on me.
Actual Behavior
Terraform crashed on me.
Steps to Reproduce
terraform init
terraform plan
Additional Context
References
The text was updated successfully, but these errors were encountered: