8 Commits (602b59cdc40c6fb0fd70817e2586cdc2db58b907)

Author	SHA1	Message	Date
Martin Atkins	e41883d972	website: Revise the "Output Values" 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. In the process of writing this, I identified some unclear statements in the "Resources" subsection, and so these are also revised here for consistency with the output values documentation.	8 years ago
Martin Atkins	6fa6a0d110	website: revise the "Resources" configuration docs section ... This is now the leading subsection of the Configuration section of the docs, and so this rewrite intends to make it more "guide-like" and as accessible as possible to those who are not yet familiar with other Terraform concepts. This rewrite also attempts to introduce some consistency into our vocabulary, which should eventually be reflected throughout our documentation. In particular: - "Resource" refers to the block the user writes in configuration, while "Resource _Type_" refers to what the provider defines. We previously used "resource" for both of these interchangeably. - "Resource" is no longer used to refer to what gets created and managed in remote APIs as a result of a resource block in configuration. Lacking a good distinct name for these, this guide uses the word "object", qualifying it as "infrastructure object" or "remote object" where necessary to retain clarity. This distinction is important to enable a clear description of resource lifecycle. - "Argument" refers to an element (attribute or block) within a resource block. This terminology was already being used in some places, so we embrace it here as a way to distinguish from "attribute", which is what a resource _exports_ for use in expressions. - Since interpolation is no longer needed to use expressions in the language, the word "expression" is used to describe the definition of a value that might involve some computation. Where necessary, this is used with a modifier "arbitrary expression" to contrast with situations where the set of allowed expression constructs is constrained.	8 years ago
Quinn Diggity	c943caf1a5	website: fix for typo in resources.html.md (#18266) ... should be provides, not provies	8 years ago
Dominik-K	9da5f5a9f0	docs: no interpolations in `lifecycle` attribute (#3116) (#17695) ... * docs: interpolations in `lifecycle` unsupported currently	8 years ago
James Bardin	ff8d02cd25	remove old warning care create_before_destroy ... Create-before-destroy dependencies are automatically ordered correctly by terraform. Remove the old notice about requiring all dependencies to have the same setting for create_before_destroy.	8 years ago
Cameron Childress	ae33b68e68	website: An example of referencing resources with "count"	8 years ago
Alexandru Ungur	9f1a773655	website: fix broken link from resources to multiple provider instances	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