Tag See all →

#for-each

3 stories

DevOps & CI/CD Bug Report

Terraform "Invalid for_each argument": sensitive values cannot be used as for_each keys

Isabel Ferreira · May 30, 2025 · 7 min read

After marking a variable sensitive to keep database passwords out of plan output, terraform plan failed with Invalid for_each argument. Sensitive values cannot be for_each keys because keys appear in resource addresses. How we restructured the input so keys stay public and secrets stay hidden.

Banner: Terraform for_each failing because its keys are unknown until apply

DevOps & CI/CD Bug Report

Terraform for_each set includes values that cannot be determined until apply

Ryan Pham · Apr 9, 2025 · 7 min read

A new module for DNS validation of ACM certificates failed at plan time with an Invalid for_each argument error on fresh environments. The for_each keys came from attributes only known after apply. Static keys with apply-time values made the plan work in one pass.

Banner: a row of numbered infrastructure blocks sliding one position after one is removed

DevOps & CI/CD Bug Report

Terraform count index shift: removing one list item planned to replace half our queues

John Nguyen · Feb 17, 2025 · 9 min read

We deleted one queue name from a Terraform list and the plan wanted to destroy and recreate every queue after it. count addresses resources by position; we moved to for_each with moved blocks and changed nothing in AWS.