f47c4efb1b
We previously added a hint to both resource for_each and dynamic blocks about using the "flatten" and "setproduct" situations to construct suitable collections to repeat over. However, we used the same text in both places which ended up stating that dynamic blocks can only accept map or set values, which is a constraint that applies to resource for_each (because we need to assign a unique identifier to each instance) and not to dynamic blocks (which don't have any uniqueness enforced by Terraform Core itself). To remove that contradiction with the text above which talks about what is valid here, I've just generalized this to say "collection", because the primary point of this paragraph is the "one element per desired nested block" part, not specifically what sort of collections are permitted in this location. (Text further up describes the supported types.) |
||
|---|---|---|
| .. | ||
| data-sources | ||
| expressions | ||
| files | ||
| functions | ||
| meta-arguments | ||
| modules | ||
| providers | ||
| resources | ||
| settings | ||
| state | ||
| syntax | ||
| values | ||
| attr-as-blocks.html.md | ||
| dependency-lock.html.md | ||
| index.html.md | ||