29 Commits (eebbdd6778d4a6db5cfead0198163c38f64ea0f7)

Author	SHA1	Message	Date
Nick Fagerlund	7a8dd326c6	website: Language: Update links to moved pages	5 years ago
Nick Fagerlund	83ebb9b178	website: Add big whitespace separators to recovery landing pages ... The resources, expressions, and modules pages were all split into smaller, more navigable pages, but the old URLs had accumulated a large number of deep links to their section headers. To help people recover when they click an old link, we converted those old URLs to landing pages, which preserve all of the old in-page anchors and point readers to the appropriate new destinations. However, because the new link-to-new-page sections are so small, it was kind of hard to tell which section you had clicked into! Especially if you were near the bottom of the page and the browser wasn't able to position the desired section at the very top of the window. This commit aims to improve that by putting one full screen of whitespace in between every linkable section on these landing pages. Yes, it's a hack, but you're meant to only view these pages for three seconds or so before moving on to the place you wanted to be, and this should help dispel any confusion about which place that is.	5 years ago
Nick Fagerlund	a446ecb7b7	website: Break up Expressions page into smaller chunks ... This commit converts the previous URL for this content to a landing page, which captures all of the previous in-page anchors and directs readers to the new home for each section.	6 years ago
Pam Selle	9f5f5adc0d	Merge pull request #26799 from flatiron32/patch-1 ... Remove redundant Local Named Values section	6 years ago
Jacob Tomaw	3f9abbc30d	Remove redundant Local Named Values section ... The second Local Named Values has a subset of the information the first one has and adds nothing to the documentation other than confusion.	6 years ago
Nick Fagerlund	596e529602	website: Adopt a ton of pages into the "language" layout ... As of this commit, that layout doesn't exist yet, but I'm isolating the one-line changes to their own commit to try and keep your eyes from glazing over.	6 years ago
Alex Novak	82aa2d4467	Correct annotation in expressions.html ... `false` section was missing a finishing "`"	6 years ago
Martin Atkins	67311f73fd	website: Draw better attention to for and for_each patterns ... When helping folks in the community forum, I commonly see questions around more complex patterns in transforming deep data structures into different shapes to work with for_each. We have examples of these patterns in the docs for the functions that they rely on, but they were not previously very discoverable in the main configuration language documentation sections. Here I've moved the "Using Expressions in for_each" subsection on the Resources page above some of the other sub-sections to hopefully make it easier to see, and written out in more detail the two specific patterns that answer a significant number of for_each-related user questions in the hope that readers will be more likely to realize that the links are relevant to what their goals. I also added some more elaboration about the behavior of converting from list to set in the "Using Sets" subsection, because this feature is often a user's first encounter with the set data type and I've inferred from some of the questions I've answered that a number of Terraform users don't have prior experience with set data types in other languages to draw assumptions from. Finally, I added some similar links to the for_each patterns within the for expression documentation itself, to try to make those examples more visible to those who might be discovering the documentation in a different sequence, e.g. by following a deep link shared in an answer to a question in the community forum.	6 years ago
Pam Selle	213189c3d0	Use a real resource	6 years ago
Pam Selle	885ff69c50	Update docs to generalize/use fake example vs one that could be misleading	6 years ago
Pam Selle	566f22a34e	Docs around splat	7 years ago
Martin Atkins	047733d20c	website: Full examples for for_each with flatten and setproduct ... A very common question since we launched the two repetition constructs is how to deal with situations where the input data structure doesn't match one-to-one with the desired configuration. This adds some full worked examples of two common situations that have come up in questions. To avoid adding a lot of extra content to the already-large "expressions" and "resources" pages, the main bulk of this new content lives with the relevant functions themselves as a full example of one thing they are good for, and then we'll link to them from the two general documentation sections where folks are likely to be reading when they encounter the problem.	7 years ago
Pam Selle	2a50bc6b5a	More in expressions, removed extra resource thing	7 years ago
Pam Selle	67e314dcbe	Some docs updates to clarify splat confusion	7 years ago
Nick Fagerlund	f6e648cc8b	website: Document behavior of `self` object for provisioners	7 years ago
Bendegúz Ács	8f9d368a25	Fixed typo in documentation about expressions	7 years ago
Alexander Hellbom	99c59b833e	website: fix expression typo ... exression -> expression	7 years ago
Pam Selle	1b25cb7d4a	Docs updates for data resources, update expressions ref	7 years ago
Ben Hadfield	0a1c0d6c24	website: Fix typo in Arithmetic Operators section (#21945)	7 years ago
Martin Atkins	127cbeeda2	website: Additional information about "dynamic" blocks ... Based on some common questions and feedback since the v0.12.0 release, here we add some small additional content to the documentation for "dynamic" blocks, covering how to access the keys of the collection being iterated over and how to fold multiple collections into a single one to achieve the effect of a nested iteration.	7 years ago
Justin Weissig	aa4c43b341	website: Fix typo on the "expressions" documentation page	7 years ago
Nick Fagerlund	50f76dd566	website: fix broken anchor link (to #for-expressions)	7 years ago
Martin Atkins	36bb9b462c	website: "for" expression examples to use canonical formatting ... The "terraform fmt" command produces a different canonical form than we were showing in our examples here. Our examples should always reflect the conventions applied by "terraform fmt" to avoid confusion. (This particular decision is a pragmatic one because the formatter design needs to use the same rules for the colon in the ? : conditional operator as for the colon in "for" expressions.)	7 years ago
Martin Atkins	0a9959cbe4	website: References to Resource Attributes ... Since references to attributes of resources are by far the most common reference type, and the mapping of resource type config to the attributes is not always obvious, here we give some real examples of patterns for accessing different configuration constructs within resource blocks along with the resource type's exported attributes. Since we don't have any real examples of labelled nested blocks yet (the current SDK doesn't support them) I've included a hypothetical example for now just to establish the patterns around them in preparation for beginning to introduce them as we roll out this feature in the SDK.	7 years ago
Nick Fagerlund	4a190127b9	website: Version notes: Add new -> old links to 0.12 language docs (except function pages)	7 years ago
Nick Fagerlund	9f85e6d5cc	website: Update configuration language section page titles	7 years ago
Nick Fagerlund	d2abdc23ac	website: Structural edit of configuration language docs ... This commit is a wide-ranging set of edits to the pages under /docs/configuration. Among other things, it - Separates style conventions out into their own page. - Separates type constraints and conversion info into their own page. - Conflates similar complex types a little more freely, since the distinction is only relevant when restricting inputs for a reusable module or resource. - Clarifies several concepts that confused me during edits.	7 years ago
Martin Atkins	d72d9fde16	website: Document the index and attribute syntaxes	8 years ago
Martin Atkins	39579e8d0f	website: revisions to the "Configuration Syntax" page and expressions ... This rewrite of the "Configuration Syntax" page now gives some more detail on the top-level structural constructs and de-emphasizes the name "HCL" as subordinate to "the Terraform language". It also now includes some commentary on valid identifiers and comments, and issues around character encodings and line endings. In addition, we now have a new "Expressions" page that replaces the old "Interpolation Syntax" page, covering the expression language features we inherit from HCL and how they behave in the context of Terraform. The "Expressions" page currently links to a page about the built-in functions which does not yet exist. This will be created in a later commit.	8 years ago