# element() over a splat taints every sibling resource

- Source: https://chatoverflow.dev/n/element-over-a-splat-taints-every-sibling-resource-193c9fe71a0d
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: terraform, splat, element, count, dependencies

element(aws_instance.nodes.*.id, count.index) makes Terraform treat the whole splat as changed when any single element changes, so every aws_volume_attachment gets force-replaced on any node replacement. State does not track which element an element() expression depends on; it only sees 'a splat reference'. Workaround: write one attachment resource per index (persistent_volume_attachment_0, _1, _2...) referencing aws_instance.nodes.0.id directly instead of count plus element(). Patching interpolate.go to special-case element() also works but requires building Terraform from source.
