99 Commits (03dc37fda284bc328a04af0d19db077bcfe6ba65)

Author	SHA1	Message	Date
Nick Fagerlund	2c50808bbb	website: Version notes: Add new -> old links to 0.12 language docs (function pages)	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	b726cc4ba9	website: Update H1 header of 0.12 index.html	7 years ago
Martin Atkins	954d38e870	lang: New file-hashing functions ... In prior versions, we recommended using hash functions in conjunction with the file function as an idiom for detecting changes to upstream blobs without fetching and comparing the whole blob. That approach relied on us being able to return raw binary data from file(...). Since Terraform strings pass through intermediate representations that are not binary-safe (e.g. the JSON state), there was a risk of string corruption in prior versions which we have avoided for 0.12 by requiring that file(...) be used only with UTF-8 text files. The specific case of returning a string and immediately passing it into another function was not actually subject to that corruption risk, since the HIL interpreter would just pass the string through verbatim, but this is still now forbidden as a result of the stricter handling of file(...). To avoid breaking these use-cases, here we introduce variants of the hash functions a with "file" prefix that take a filename for a disk file to hash rather than hashing the given string directly. The configuration upgrade tool also now includes a rule to detect the documented idiom and rewrite it into a single function call for one of these new functions. This does cause a bit of function sprawl, but that seems preferable to introducing more complex rules for when file(...) can and cannot read binary files, making the behavior of these various functions easier to understand in isolation.	7 years ago
Martin Atkins	2f8f7d6f4d	lang/funcs: Type conversion functions ... It's not normally necessary to make explicit type conversions in Terraform because the language implicitly converts as necessary, but explicit conversions are useful in a few specialized cases: - When defining output values for a reusable module, it may be desirable to force a "cleaner" output type than would naturally arise from a computation, such as forcing a string containing digits into a number. - Our 0.12upgrade mechanism will use some of these to replace use of the undocumented, hidden type conversion functions in HIL, and force particular type interpretations in some tricky cases. - We've found that type conversion functions can be useful as _temporary_ workarounds for bugs in Terraform and in providers where implicit type conversion isn't working correctly or a type constraint isn't specified precisely enough for the automatic conversion behavior. These all follow the same convention of being named "to" followed by a short type name. Since we've had a long-standing convention of running all the words together in lowercase in function names, we stick to that here even though some of these names are quite strange, because these should be rarely-used functions anyway.	7 years ago
Martin Atkins	da51e72cbb	lang/functions: set functions from cty ... The sethaselement, setintersection, and setunion functions are defined in the cty stdlib. Making them available in Terraform will make it easier to work with sets, and complement the currently-Terraform-specific setproduct function. In the long run setproduct should probably move into the cty stdlib too, but since it was submitted as a Terraform function originally we'll leave it here now for simplicity's sake and reorganize later.	7 years ago
Martin Atkins	edb5f82de1	lang/funcs: Convert the "setproduct" function to the new approach ... In our new world it produces either a set of a tuple type or a list of a tuple type, depending on the given argument types. The resulting collection's element tuple type is decided by the element types of the given collections, allowing type information to propagate even if unknown values are present.	7 years ago
Martin Atkins	d0e6a4c69a	lang: Add "formatdate" function ... We missed this one on a previous pass of bringing in most of the cty stdlib functions. This will resolve #17625 by allowing conversion from Terraform's conventional RFC 3339 timestamps into various other formats.	7 years ago
Martin Atkins	c753df6a93	lang/funcs: templatefile function ... This function is similar to the template_file data source offered by the template provider, but having it built in to the language makes it more convenient to use, allowing templates to be rendered from files anywhere an inline template would normally be allowed: user_data = templatefile("${path.module}/userdata.tmpl", { hostname = format("petserver%02d", count.index) }) Unlike the template_file data source, this function allows values of any type in its variables map, passing them through verbatim to the template. Its tighter integration with Terraform also allows it to return better error messages with source location information from the template itself. The template_file data source was originally created to work around the fact that HIL didn't have any support for map values at the time, and even once map support was added it wasn't very usable. With HCL2 expressions, there's little reason left to use a data source to render a template; the only remaining reason left to use template_file is to render a template that is constructed dynamically during the Terraform run, which is a very rare need.	7 years ago
Nick Fagerlund	17873ae61b	website: Update functions section page titles	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
Nick Fagerlund	7d5db9522f	website: Fix plugin path on Windows (#19423) ... ...and one other reference to the application data directory. Context: https://docs.microsoft.com/en-us/windows/desktop/shell/knownfolderid#folderid_roamingappdata In newer Windows versions, the folder accessible as `%APPDATA%` (and via various APIs) is actually at something like "documents and settings\user\application data\roaming", while earlier versions omit the "\roaming" part of the path. This means you can confuse people by referring to the "application data" directory by its human name, because "roaming" is the real application data directory, but it looks like a subdirectory of "application data". Thus, it's less confusing to just use the `%APPDATA%` variable, with the added benefit that you can copy and paste the path and it'll just work in most places.	8 years ago
Michael Irwin	47047aa637	Small grammar fix for lifecycle docs	8 years ago
Radek Simko	edaa4bbc82	lang: Add fileexists function	8 years ago
Martin Atkins	1360948a41	website: document the functions "keys", "lookup", and "values" ... I missed these on the first pass because in the legacy function table they are, for some reason, added in a different place than the others.	8 years ago
Kristin Laemmert	b6d3d69d3a	port cidr functions	8 years ago
Kristin Laemmert	602b59cdc4	porting functions	8 years ago
Kristin Laemmert	9aa9b18658	porting crypto functions	8 years ago
Kristin Laemmert	1a5299efcb	porting encoding functions	8 years ago
Martin Atkins	60ad24229f	website: Link from Configuration index to Resource page ... Since the index page is long, by the time the reader reaches the end of it the relevant portion if the navigation is unlikely to be visible. To compensate for this, we'll link to the first sub-section and thus give the user an opportunity to notice the navigation structure for the rest of the pages.	8 years ago
Martin Atkins	6549f24d88	website: Remove the "interpolation" docs page ... This has now been superseded by the expressions.html.md file in the same directory. As part of deploying this, the former URL for this page must be redirected to the expressions page to retain a target for any existing links on third-party sites.	8 years ago
Martin Atkins	c060ecd0a5	website: Document the JSON configuration syntax	8 years ago
Martin Atkins	a6749f9efc	website: Expand documentation of Override Files ... This kinda-weird feature was previously quite severely under-documented in terms of exactly what effect it has. This new documentation for it first attempts to frame it as something that should be rarely used, and then explains in more detail exactly how it behaves for different top-level block types within the configuration.	8 years ago
Martin Atkins	b3239e8f1f	website: Update the "Terraform Settings" page for new style ... As part of revamping the "Configuration" portion of the website for the v0.12 release, here we update the Terraform Settings page to use a similar "guide-like" writing style as the other updated pages in this section.	8 years ago
Martin Atkins	d72d9fde16	website: Document the index and attribute syntaxes	8 years ago
Martin Atkins	83a16e3deb	website: Docs for all of the IP address calculation functions	8 years ago
Martin Atkins	7cb1de9f30	website: Docs for all of the hash/crypto functions	8 years ago
Martin Atkins	46f8208727	website: Docs for all of the Date and Time functions	8 years ago
Martin Atkins	a35c0f3cbf	website: Docs for all of the "filesystem" functions	8 years ago
Martin Atkins	a491013054	website: Docs for all of the "encoding" functions	8 years ago
Martin Atkins	e7d71995f6	website: Document the remaining "collection" functions ... This also renames some of the existing function pages whose source filenames were not matching the usual naming scheme (.html.md).	8 years ago
Martin Atkins	48d940323e	website: Beginnings of "Functions" configuration section ... Previously we just listed out all of the functions in alphabetical order inside the "Interpolation Syntax" page, but that format doesn't leave much room for details and usage examples. Now we give each function its own page, and categorize them for easier navigation. While many functions are very simple and don't really warrant a full page, certain functions do have additional details that are worth mentioning and this structure scales better for those more complicated functions. So far this includes only the numeric and string functions. Other categories will follow in subsequent commits.	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
Martin Atkins	e1754970a8	website: Revise the "Data Sources" 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. The data sources page has not got any real attention since the feature was first added, and our vocabulary for describing them and their lifecycle hadn't quite settled when the page was originally written. This new version is consistent in how it uses "data source" to describe the feature that providers offer and "data resource" to describe what is created by a "data" block in configuration, which then allows us to draw on the many shared features between both data and managed resources. For the moment this waits until "data resource" is defined in order to first introduce the qualifier "managed resource". We may wish to revise this again to mention that more specific nomenclature in passing on the "Resources" page, in case a user encounters it elsewhere and wants to learn what it means without needing to be familiar with data resources first.	8 years ago
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	fdc8bb6c00	website: Revise the "Local 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.	8 years ago
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	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
Martin Atkins	a6cf796873	website: Revise the "Providers" configuration docs section ... These revisions reflect this sub-section's new earlier placement in the sub-section list, leading to a more guide-like style for the initial sections. Also includes some minor copy-editing to align terminology with that introduced in the prior commit for the "Resources" docs page.	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
Martin Atkins	27429b61a9	website: Flesh out the intro to the "Configuration" section. ... The prior content on this page was little more than an instruction to begin navigating the sub-sections of this section. The new content aims to give a broad overview of some of the language concepts and a syntax example, in order to create some context to help the user navigate the subsections more easily. This also introduces for the first time usage of the term "the Terraform language". This was previously left un-named, leading to some awkward sentence constructions elsewhere in the docs. This new name gives us some specific terminology to use in order to contrast the language that exists at Terraform's level of abstraction, defining the semantics, from the underlying grammar provided by HCL.	8 years ago
Martin Atkins	e5e3452ffa	website: Reorganize the "Configuration" docs section ... With the additional configuration language features coming in Terraform v0.12, our existing documentation structure is beginning to strain. Here we reorganize the navigation slightly in order to introduce the concepts in a more appropriate order so that we can reveal complexity more gradually. Subsequent commits will revise the content of these pages to better reflect the new sequencing. The "Environment Variables" page is moved from the Configuration section into the "Commands" section, since it is not considered a part of the configuration language and thus more appropriate in the CLI documentation. The old placement is reflective of the broader purpose that the "Configuration" section had originally, but its new focus will be on the Terraform language (.tf files) in particular, with other aspects of customizing Terraforms behavior covered in other sections.	8 years ago
Nick Fagerlund	b3935b29d7	website: Reconcile docs about plugin discovery and downloading (#18973) ... website: Reconcile docs about plugin discovery and downloading I'm attempting to keep things simple for normal users while making sure we've got the full behavior written down somewhere for plugin developers. This commit doesn't stand alone; it's paired with a commit in the terraform-website repo, to deal with some related content in the "extend" section.	8 years ago
saravanan palanisamy	517e28ee6e	update uuid definition	8 years ago
Quinn Diggity	c943caf1a5	website: fix for typo in resources.html.md (#18266) ... should be provides, not provies	8 years ago
Paddy	931f8ecc41	Fix broken links to /docs/enterprise/run/api.html ... We had a couple broken links pointing to the docs for the run API. This updates them to the new location.	8 years ago
Jaye Doepke	596c7b2638	docs typo	8 years ago
SpencerBrown	3324de35b6	Fix typo in doc: "The support operators are" -> "The supported operators are"	8 years ago
Dominik-K	9da5f5a9f0	docs: no interpolations in `lifecycle` attribute (#3116) (#17695) ... * docs: interpolations in `lifecycle` unsupported currently	8 years ago