362 Commits (4cffff24b1d1e0af43aed445e411f4e9cc6e6238)

Author	SHA1	Message	Date
Robin Norwood	ec7d9c85ac	Update link to new varibles tutorial	6 years ago
Joshua Mendoza	27e31e1160	Update lookup.html.md (#26835) ... Typo in introductory paragraph.	6 years ago
Martin Atkins	ae3c0c6a4a	lang/funcs: Remove the deprecated "list" and "map" functions ... Prior to Terraform 0.12 these two functions were the only way to construct literal lists and maps (respectively) in HIL expressions. Terraform 0.12, by switching to HCL 2, introduced first-class syntax for constructing tuple and object values, which can then be converted into list and map values using the tolist and tomap type conversion functions. We marked both of these functions as deprecated in the Terraform v0.12 release and have since then mentioned in the docs that they will be removed in a future Terraform version. The "terraform 0.12upgrade" tool from Terraform v0.12 also included a rule to automatically rewrite uses of these functions into equivalent new syntax. The main motivation for removing these now is just to get this change made prior to Terraform 1.0. as we'll be doing with various other deprecations. However, a specific reason for these two functions in particular is that their existence is what caused us to invent the idea of a "type expression" as a distinct kind of expression in Terraform v0.12, and so removing them now would allow potentially unifying type expressions with value expressions in a future release. We do not have any current specific plans to make that change, but one potential motivation for doing so would be to take another attempt at a generalized "convert" function which takes a type as one of its arguments. Our previous attempt to implement such a function was foiled by the fact that Terraform's expression validator doesn't have any way to know to treat one argument of a particular function as special, and so it was generating incorrect error messages. We won't necessarily do that, but having these "list" and "map" functions out of the way leaves the option open.	6 years ago
Radek Simko	eddcc4d80c	docs: Fix typo (provider arg in data source) (#26802)	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
timvandamme	fbf267fbfd	website: for_each doesn't implicitly convert to set (#26450) ... The documentation states that an explicit type conversion to set is needed, but it does not say why implicit type conversion does not work. Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	6 years ago
Radek Simko	a413fa7425	Merge pull request #26763 from hashicorp/radeksimko-patch-1 ... docs: fix typo in provider local name	6 years ago
Repon Kumar Roy	34549b402b	website: clarify version constraint syntax	6 years ago
Nick Fagerlund	a058b64eb5	website: Index for `element` must be a non-negative integer (#26679) ... * The index must be non-negative integer and added instructions on how to get the last value in the list. * Typo fix Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	6 years ago
Nick Fagerlund	5a4957f141	Typo fix	6 years ago
Nick Fagerlund	a0fee4c380	website: one more provider name typo	6 years ago
Radek Simko	8476c3f13e	docs: fix typo in provider local name	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 Litvinenko	1a371c3c49	Small spelling improvement ... It seems that the word `with` is redundant in the following sentence: > For a module with without count or for_each, the address will not...	6 years ago
Kristin Laemmert	b8e3b8036a	backend: remove deprecated atlas backend	6 years ago
Martin Atkins	ddf9635af6	website: Don't claim that things are "very easy" ... We typically try to avoid making subjective, boasty claims in our documentation in recent times, but there remained both some older documentation that we've not recently revised and also some newer examples that are, in retrospect, also perhaps more "boasty" than they need to be. We prefer not to use this sort of boasty language because not everyone using Terraform has the same background and experience, and so what is "easy" or "intuitive" to one person may not be so to another person, and that should not suggest that the second person is in any way wrong or inadequate. In reviewing some of our use of the word "easy" here I tried as much as possible to surgically revise the existing content without getting drawn into a big rewrite, but in some cases the content was either pretty unsalvageable (due to talking about obsolete features that were removed long ago) or required some broader changes to make the result hopefully still get the same facts across. In those cases I've both removed some content entirely or adjusted larger paragraphs. This was not an exhaustive review and so I'm sure there's still plenty of room for similar improvements elsewhere. I also resisted the urge to update some pages that contain outdated information about currently-active features.	6 years ago
Arthur Burkart	d4716a69e1	lang/funcs: "anytrue" function ... This is an analog to the "alltrue" function, using OR as the reduce operator rather than AND. This also includes some simplification of the "alltrue" implementation to implement it similarly as a sort of reduce operation with AND as the reduce operator, but with the same effective behavior.	6 years ago
Petros Kolyvas	b1671b2ce1	website: Fix for documentation around local-name conflicts (#26689) ... * Fixes #26684 * Update provider-requirements.html.md Removing additional/extra newlines * Update provider-requirements.html.md And now some trailing spaces. le sigh	6 years ago
craiggenner	6408533fca	The index must be non-negative integer ... and added instructions on how to get the last value in the list.	6 years ago
Martin Atkins	1dc4950bfa	lang/funcs: Rename the base64 character encoding functions ... These were initially introduced as functions with "encode" and "decode" prefixes, but that doesn't match with our existing convention of putting the encoding format first so that the encode and decode functions will group together in a alphabetically-ordered function list. "text" is not really a defined serialization format, but it's a short word that hopefully represents well enough what these functions are aiming to encode and decode, while being consistent with existing functions like jsonencode/jsondecode, yamlencode/yamldecode, etc. The "base64" at the end here is less convincing because there is precedent for that modifier to appear both at the beginning and the end in our existing function names. I chose to put it at the end here because that seems to be our emergent convention for situations where the base64 encoding is a sort of secondary modifier alongside the primary purpose of the function, as we see with "filebase64". (base64gzip is an exception here, but it seems outvoted by the others.)	6 years ago
r0bnet	877399c631	lang/funcs: Functions for encoding text in specific character encodings	6 years ago
Martin Atkins	0bbbb9c64b	configs: Experimental support for optional object type attributes ... This builds on an experimental feature in the underlying cty library which allows marking specific attribtues of an object type constraint as optional, which in turn modifies how the cty conversion package handles missing attributes in a source value: it will silently substitute a null value of the appropriate type rather than returning an error. In order to implement the experiment this commit temporarily forks the HCL typeexpr extension package into a local internal/typeexpr package, where I've extended the type constraint syntax to allow annotating object type attributes as being optional using the HCL function call syntax. If the experiment is successful -- both at the Terraform layer and in the underlying cty library -- we'll likely send these modifications to upstream HCL so that other HCL-based languages can potentially benefit from this new capability. Because it's experimental, the optional attribute modifier is allowed only with an explicit opt-in to the module_variable_optional_attrs experiment.	6 years ago
Martin Atkins	897cb72b36	website: Initial docs for the new dependency lock file behaviors ... This includes both the main documentation about the lock file itself and changes to related documentation about Terraform commands that interact with the lock file. We will likely continue to update this first pass of documentation as we get feedback and questions during the prerelease period.	6 years ago
Pam Selle	9a9e61ef06	Update docs for output sensitivity change	6 years ago
Pam Selle	cc007a27b7	Merge pull request #26482 from hashicorp/pselle/sensitive-var-nested-docs ... Add sensitive variable docs for nested blocks	6 years ago
Pam Selle	4d01fc88fc	Add sensitive variable docs for nested blocks ... Add note to docs about nested block behavior for sensitive variables	6 years ago
JT Smith	6ac8bfb86d	[Documentation] Typo fixes ... Just re-read the docs the ignore_changes update and saw a few typos	6 years ago
James Bardin	ee564a5ceb	Merge pull request #26421 from hashicorp/jbardin/ignore-changes-map ... allow ignore_changes to reference any map key	6 years ago
Nick Fagerlund	26f786959b	website: Update all Learn crosslinks (#26442) ... * website: Update all Learn crosslinks The URL structure on Learn recently changed, so it's time to update some URLs. Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	6 years ago
Pam Selle	a7e43dfd46	Merge pull request #26431 from hashicorp/pselle/sensitive-vals-docs ... docs: Docs for sensitive variables	6 years ago
Pam Selle	3ddbb4b009	Update provider caveat grammar	6 years ago
Pam Selle	93d38ff2d2	Update intro to code blocks	6 years ago
Pam Selle	be50089c7f	Rephrase sensitive index description	6 years ago
Pam Selle	09551de078	Rewrite intro to section, rename section, move state info ... Move the information about state from the "caveats" to the main info section, using similar information to sensitive outputs. Updates the header of the section from similar inspiration.	6 years ago
Pam Selle	5cf61448e7	Update website/docs/configuration/variables.html.md ... Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	6 years ago
James Bardin	82793f8158	update ignore_changes doc ... We can remove the caveat about changing map elements. Add a little more text about the intended use case for ignore_changes, as the common case of fixing erroneous provider behavior should not be the primary motivation for the maintenance of this feature.	6 years ago
Pam Selle	2a35240a17	Merge pull request #26314 from hashicorp/remove-template-provider-link ... docs: remove link to deprecated provider	6 years ago
Pam Selle	e369fe0559	Docs for sensitive variables	6 years ago
Pam Selle	b57248533d	Re-organize variable page for sensitive argument addition	6 years ago
Alejandro Rosero Vicuña	6d66b8b616	website: Make template file extension more consistent (#25029) ... Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	6 years ago
Arthur Burkart	6ed47c7241	lang/funcs: Add "alltrue" function (#25656) ... This commit adds an `alltrue` function to Terraform configuration. A reason we might want this function is because it will enable more powerful custom variable validations. For example: ```hcl variable "amis" { type = list(object({ id = string })) validation { condition = (alltrue([ for a in var.amis : length(a.id) > 4 && substr(a.id, 0, 4) == "ami-" ])) error_message = "The ID of at least one AMI was invalid." } } ```	6 years ago
kmoe	f12bb4698e	remove link to deprecated provider	6 years ago
Brian Flad	db2b710776	docs/function/timestamp: Mention Time Provider (#26232) ... This utility Terraform Provider has resources designed to handle and store time information by participating normally in the graph.	6 years ago
Petros Kolyvas	2167f92096	website: Adding a note around data-sources and depends_on for 0.12 users (#26222) ... * Adding not about data-sources and depends-on for 0.12 users * Bold * A little more markdown * A little more markdown for data_sources in 0.12 * Some iteration based on good feedback	6 years ago
Jon "The Nice Guy" Spriggs	6f9ce7310c	Website: Add map example to templatefile function docs (#26126) ... This change adds an example of using a map with a few keys and shows how it runs it. Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	6 years ago
Pam Selle	5ec1868419	Merge pull request #25864 from alexnovak/patch-1 ... Correct annotation in expressions.html	6 years ago
Kristin Laemmert	923e157b5c	configs: deprecate version argument inside provider configuration blocks (#26135) ... The version argument is deprecated in Terraform v0.14 in favor of required_providers and will be removed in a future version of terraform (expected to be v0.15). The provider configuration documentation already discourages use of 'version' inside provider configuration blocks, so it only needed an extra note that it is actively deprecated.	6 years ago
Alisdair McDiarmid	9f19034fee	website: Document jsonencode entity escaping	6 years ago
Nick Fagerlund	56c0e35243	website: Fix copy-paste error	6 years ago
Nick Fagerlund	a4776bfb40	website: Clarify `locals` vs. `local.thing` distinction ... The subtle difference in keywords when creating vs. accessing locals trips people up, even more than the "variable" vs. "var" distinction. It deserves its own subheader on the page, plus a nice noisy callout.	6 years ago
Lance Kind	eb7a427fba	Update locals.html.md ... I've just wasted an hour to two hours trying to find the problem to finally realize that although I declare a "locals" block, it's referred to as "local". This is pretty weird! So let's be be clear about this.	6 years ago
Jai Govindani	d8b36e5d12	style(providers): update syntax for terraform >= 0.11	6 years ago
Pam Selle	f2d213c461	Merge pull request #25657 from pdecat/typo_hierarchical ... Typo: heirarchical => hierarchical	6 years ago
Roger Berlind	3070f21241	Fix foreach to for_each ... `foreach` on modules should be `for_each`	6 years ago
Kristin Laemmert	4569a37de4	website/docs: provider source related clarifications	6 years ago
Kristin Laemmert	75e676f2f2	website/docs: remove unclear provider version constraint description (#25998)	6 years ago
Alisdair McDiarmid	93cd6b1b75	Merge pull request #25989 from pdecat/patch-1 ... Fix link to "v0.12-Compatible Provider Requirements" section	6 years ago
Alisdair McDiarmid	5f43934d5f	website: Provider requirements are not inherited ... Add a note to the provider configuration section explaining that only config can be inherited by child modules, not source or version requirements.	6 years ago
Patrick Decat	84c50f9efb	Fix link to "v0.12-Compatible Provider Requirements" section ... On the https://www.terraform.io/docs/configuration/provider-requirements.html#requiring-providers page, the link to the `v0.12-Compatible Provider Requirements` section is broken: * current link: https://www.terraform.io/docs/configuration/provider-requirements.html#v012-compatible-provider-requirements * correct link: https://www.terraform.io/docs/configuration/provider-requirements.html#v0-12-compatible-provider-requirements	6 years ago
Alex Novak	82aa2d4467	Correct annotation in expressions.html ... `false` section was missing a finishing "`"	6 years ago
Kristin Laemmert	7111d8deb1	Merge pull request #25783 from nvogel/master ... Fix documentation example for the indent function	6 years ago
Nick Fagerlund	2ffb71bcee	website: Fix several broken links (#25808)	6 years ago
Nicolas Vogel	8f42f0fa77	Fix documentation example for the indent function ... We must use interpolation, using the %{} directive will trigger the following error "indent" is not a valid template control keyword	6 years ago
Nick Fagerlund	0ab7c1b90e	website: Add links to relevant Learn guides in several docs pages (#25718) ... Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	6 years ago
Nick Fagerlund	0e5651560b	Website: 0.13 docs edits, mostly around provider requirements (#25686) ... * Make sidebar nav in language docs more intuitive * Minor display fixes for registry docs * Explain providers in the registry in the providers index * Revise a bunch of language docs around provider reqs This is mostly an effort to smooth out some of the explanations, make sure things are presented in a helpful order, make sure terminology lines up, draw connections between related concepts, make default behavior more apparent, and the like. It shouldn't include very much new information, but there might be one or two things that came out of a conversation somewhere. Co-authored-by: Judith Malnick <judith@hashicorp.com>	6 years ago
Martin Atkins	ef071f3d0e	website: Generalized advice on modules with provider configs ... As part of documenting the new module for_each capabilities we added a section noting that shared modules using the legacy pattern of declaring their own provider configurations would not be compatible with them. However, that also applies to the new module depends_on and several folks participating in the beta pointed out that the documentation wasn't discussing that at all. In order to generalize the advice, I've moved the old content we had (since v0.11) recommending against provider configurations in shared modules out into its own section, now being more explicit that it is a legacy pattern and not recommended, and then folded the content about for_each and count, now also including depends_on, into that expanded section. As is often the case, that had some knock-on effects on the content on the rest of this page, so there's some general editing and reorganization here. In particular, I moved the "Multiple Instances of a Module" section much further up the page because it's content relevant to users of shared modules, while the later content on this page is more aimed at authors of shared modules, including the new section about the legacy pattern.	6 years ago
Patrick Decat	062865735f	Typo: heirarchical => hierarchical	6 years ago
MorganGeek	3b6c1ef156	Fix spelling mistakes/typos in documentation	6 years ago
Kristin Laemmert	c4ce84269a	website/docs: document difference in formatting strings with width and precision (#25499)	6 years ago
Martin Atkins	02b130cd59	website: Terraform v0.13 upgrade guide	6 years ago
Alisdair McDiarmid	c093c50c80	Merge pull request #25255 from unki/patch-1 ... fix yamldecode()-example, missing a file() call	6 years ago
jessica-ritter	edbf59ed4c	what happens when prefix is not in string ... https://github.com/hashicorp/terraform/blob/master/lang/functions.go#L126 shows that Terraform's Trimprefix comes directly from the standard go library. When prefix is absent in the go standard library, the original string is returned; https://golang.org/pkg/strings/#TrimPrefix.	6 years ago
Martin Atkins	dc8fd14c1e	website: "Provider Requirements" documentation ... We previously covered everything about using providers on a single page, but that was getting unwieldy already and we now have a lot more to discuss with v0.13 introducing a new source address syntax and some other concepts. Here we split the provider-related content into two parts: "Provider Requirements" covers how to find and declare dependencies on providers, and then "Provider Configuration" (formerly just "Providers") then focuses primarily on how to write zero or more provider configurations for a particular provider. Because "Provider Requirements" is now presented before "Provider Configuration" in the navigation, I've also moved some of the introductory content about providers in general onto the "Requirements" page. The first paragraph of that content is duplicated onto the "Configuration" page for discoverability, but we now link to the requirements page to get the full story.	6 years ago
Nick Fagerlund	b1eb9dcfcf	website: Configuration Language navigation refactoring ... The "Configuration Language" section was becoming rather unweildy, both by having a lot of pages and by some of the pages being quite large in themselves. This is a first step towards breaking things up a little more, starting with two changes: - The "Configuration Language" navigation is now split into two sub-headings "Configuration Blocks" and "Syntax". - Some of the information about sub-blocks of the "terraform" block are now given their own pages, because their content is quite complex in itself. - "Version Constraints" is now a page in its own right, rather than this content being duplicated in slightly different forms across multiple contexts that make use of user-specified version constraints.	6 years ago
unki	214009e0f3	fix yamldecode()-example, missing a file() call	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
James Bardin	866449a78a	Merge pull request #25069 from hashicorp/jbardin/depends-on-docs ... depends_on doc updates	6 years ago
Martin Atkins	d1bc412220	configs: Custom variable validation is no longer experimental ... All of the feedback from the experiment described enhancements that can potentially be added later without breaking changes, so this change simply removes the experiment gate from the feature as originally implemented with no changes to its functionality. Further enhancements may follow in later releases, but the goal of this change is just to ship the feature exactly as it was under the experiment. Most of the changes here are cleaning up the experiment opt-ins from our test cases. The most important parts are in configs/experiments.go and in experiments/experiment.go .	6 years ago
James Bardin	5d64029275	depends_on doc updates ... Update depends_on for modules and data sources.	6 years ago
Garron Kramer	f3db1232a0	Update modules.html.md ... the -module option is no longer present.	6 years ago
Daniel Dreier	44e3d99409	Merge pull request #24659 from hashicorp/timestamp-doc ... specify that `timestamp` returns UTC	6 years ago
Daniel Dreier	5e35dedc2a	Update website/docs/configuration/functions/timestamp.html.md ... Co-authored-by: Matthew Sanabria <24284972+sudomateo@users.noreply.github.com>	6 years ago
Daniel Dreier	5f80f6d49d	Merge pull request #24771 from bradleypmartin/issue-24198-update-docs-for-map-type ... Update maps docs to reflect v0.12 colon behavior	6 years ago
Daniel Dreier	5ef80b35e3	Merge pull request #24996 from pcleddy/foreach_with_toset_and_list ... Example of for_each with list -> set using toset	6 years ago
Pam Selle	bfbdb4cb1d	Add docs for provider limitations when expanding modules (#25007) ... * Add docs for provider limitations when expanding modules	6 years ago
Paul Leddy	3d17c87698	Example of for_each with list -> set using toset	6 years ago
Jean Dupouy	a54bb124a9	website/docs: provider aliases in the JSON format ... Fixes #24889	6 years ago
Robin Norwood	af5c425360	website: Add link to new learn track in configuration/modules.html (#24847)	6 years ago
Daniel Dreier	7aa97f415d	Fix "additoinal" typo in web site ... Fixes 24769	6 years ago
bradleypmartin	0b45a3c83d	Update maps docs to reflect v0.12 colon behavior	6 years ago
Martin Atkins	c6cbbcb79a	website: Initial documentation for provider_installation in the CLI config ... This is an initial draft of documentation for this new feature of the CLI configuration. This is mainly intended as a placeholder for now, because there are other documentation updates pending for the new provider namespacing and installation scheme and we'll likely want to revise these docs to better complement the broader documentation once it's written.	6 years ago
Noah Mercado	d4d8812afa	Feature: Sum Function (#24666) ... The sum function takes a list or set of numbers and returns the sum of those numbers.	6 years ago
Namho Kim	9cc658b491	specify that `timestamp` returns UTC	6 years ago
Pam Selle	ab101f99df	Merge pull request #24635 from hashicorp/pselle/docs-mod-count ... Docs for count/for_each on modules	6 years ago
Pam Selle	608c17d518	Update providers block notes	6 years ago
Fred	76f583ac9f	website/docs: fix broken hcl json spec link (#24630)	6 years ago
Pam Selle	65c4ba9c85	First docs for count/for_each on modules	6 years ago
Eduard Tamsa	534ba630e4	docs(flatten): Fix typos (#24492)	6 years ago
Adam Leskis	4f85a1a6ba	website: fix simple typo (#24415)	6 years ago
Paddy	e6592dc710	Add support for provider metadata to modules. (#22583) ... Implement a new provider_meta block in the terraform block of modules, allowing provider-keyed metadata to be communicated from HCL to provider binaries. Bundled in this change for minimal protocol version bumping is the addition of markdown support for attribute descriptions and the ability to indicate when an attribute is deprecated, so this information can be shown in the schema dump. Co-authored-by: Paul Tyng <paul@paultyng.net>	6 years ago