Terraform Crash

[shivamgupta01]

Terraform Version

... 12.6

Terraform Configuration Files

...

Debug Output

Crash Output

panic: not a string

goroutine 136 [running]:
github.com/hashicorp/terraform/vendor/github.com/zclconf/go-cty/cty.Value.AsString(...)
/go/src/github.com/hashicorp/terraform/vendor/github.com/zclconf/go-cty/cty/value_ops.go:1026
github.com/hashicorp/terraform/vendor/github.com/zclconf/go-cty/cty.Value.AsValueMap(0x222aa20, 0xc0001d6320, 0x19c94a0, 0xc0001d6340, 0x3)
/go/src/github.com/hashicorp/terraform/vendor/github.com/zclconf/go-cty/cty/value_ops.go:1095 +0x38a
github.com/hashicorp/terraform/terraform.evaluateResourceForEachExpressionKnown(0x2229960, 0xc00039c780, 0x225ab20, 0xc00088f1e0, 0x1c, 0xc0001c0a10, 0x19ecec0, 0x0, 0x19ecec0)
/go/src/github.com/hashicorp/terraform/terraform/eval_for_each.go:84 +0x5bd
github.com/hashicorp/terraform/terraform.evaluateResourceForEachExpression(0x2229960, 0xc00039c780, 0x225ab20, 0xc00088f1e0, 0x1, 0x1, 0x0, 0x0)
/go/src/github.com/hashicorp/terraform/terraform/eval_for_each.go:17 +0x5c
github.com/hashicorp/terraform/terraform.(*NodeRefreshableManagedResource).DynamicExpand(0xc0005391b8, 0x225ab20, 0xc00088f1e0, 0x0, 0x0, 0x0)
/go/src/github.com/hashicorp/terraform/terraform/node_resource_refresh.go:42 +0x280
github.com/hashicorp/terraform/terraform.(*Graph).walk.func1(0x1ce5120, 0xc0005391b8, 0x0, 0x0, 0x0)
/go/src/github.com/hashicorp/terraform/terraform/graph.go:103 +0x8b1
github.com/hashicorp/terraform/dag.(*Walker).walkVertex(0xc000495180, 0x1ce5120, 0xc0005391b8, 0xc00088aec0)
/go/src/github.com/hashicorp/terraform/dag/walk.go:392 +0x353
created by github.com/hashicorp/terraform/dag.(*Walker).Update
/go/src/github.com/hashicorp/terraform/dag/walk.go:314 +0xa9b

Expected Behavior

Actual Behavior

Steps to Reproduce

Additional Context

References

[hashibot]

Hello! 🤖

This issue seems to be covering the same problem or request as #22580, so we're going to close it just to consolidate the discussion over there. Thanks!

[ghost]

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.