9 Commits (b8df11bc331c8b7477f3ccc3cd6ec49ffc931757)

Author	SHA1	Message	Date
Martin Atkins	eeb96b1e12	website: Revise the "Modules" configuration docs section ... This adopts a more guide-like writing style, similar to what prior commits have done to some other subsections of this section. Since we already have a whole top-level section devoted to modules, there is no need for full coverage of all of their features here. Instead, this section focuses on an an initial introduction to what modules are and the basics of their usage within the Terraform language. We then link to the main modules section for the full details.	8 years ago
Martin Atkins	f8f2ff2202	website: Revise the "Input Variables" configuration docs section ... This adopts a more guide-like writing style, similar to what prior commits have done to the Resources and Providers sections.	8 years ago
Andrew	2b68f4393e	website: explanation of TF_VAR_ precedence ... Fixes #15595	8 years ago
Martin Atkins	f3a2165587	website: Use "Input Variable" as full term for var.foo ... We've historically been somewhat inconsistent in how we refer to the type of object defined by "variable" blocks in configuration. Parts of our documentation refer to them as "input variables" or just "variables", while our implementation refers to them as "user variables". Since Terraform Registry is now also referring to these as "Inputs", here we standardize on "Input Variable" as the fully-qualified name for this concept, with "variable" being a shorthand for this where context is obvious. Outside of this context, anything that can be referred to in an interpolation expression is generically known as a "variable", with Input Variables being just one kind, specified by the "var." prefix. While this terminology shift is not critical yet, it will become more important as we start to document the new version of the configuration language so we can use the generic meaning of "variable" there.	9 years ago
Martin Atkins	91a4af9c8a	website: rewrite modules usage documentation for new features ... The modules mechanism has changed quite a bit for version 0.11 and so although simple usage remains broadly compatible there are some significant changes in the behavior of more complex modules. Since large parts of this were rewritten anyway, I also took the opportunity to do some copy-editing to make the prose on this page more consistent with our usual editorial voice and to wrap the long lines.	9 years ago
Chris Doherty	793b986860	Cosmetic doc changes: ... - Having a map 'foo' with a key 'foo' is confusing. - it's -> its	9 years ago
Robert Liebowitz	8d98fdecac	Autoload only .auto.tfvars files	9 years ago
Robert Liebowitz	006744bfe0	Use all tfvars files in working directory ... As a side effect, several commands that previously did not have a failure state can now fail during meta-parameter processing.	9 years ago
Martin Atkins	7ed70bb00e	website: new filesystem layout for core/provider split ... This repo now contains only the core docs, with other content moving elsewhere.	9 years ago