9 Commits (1dabdf0dcd5ab48bf706177da8ffeda89e323dc2)

Author	SHA1	Message	Date
Laura Pacilio	87348f97f8	Update website/docs/language/expressions/dynamic-blocks.html.md ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Laura Pacilio	ad9fb34c0b	Remove backticks from dynamic blocks page	5 years ago
Laura Pacilio	a780f625e9	Fix metadata description format on all pages	5 years ago
Laura Pacilio	bc9065334e	Update description metadata per PR feedback	5 years ago
Laura Pacilio	eebbdd6778	Update dynamic blocks description with more detail and to remove 'ing'	5 years ago
Laura Pacilio	df16096141	Add description metadata to dynamic blocks, types, and module providers	5 years ago
Martin Atkins	f47c4efb1b	website: Dynamic blocks can for_each any collection type ... 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.)	5 years ago
Nick Fagerlund	7a8dd326c6	website: Language: Update links to moved pages	5 years ago
Nick Fagerlund	78dcc8dc1b	website: Language: Move files to match new URL structure	5 years ago