1229 Commits (edb4c00a8616d2b284febe618f13b9d925b1984f)

Author	SHA1	Message	Date
Rémy Léone	edb4c00a86	website: add links to the registry provider documentation (#27416) ... * docs: add links to the registry provider documentation * Adjust wording/link URL Co-authored-by: Nick Fagerlund <nick@hashicorp.com>	5 years ago
Nick Fagerlund	303b326008	Merge pull request #27279 from kowshikRoy/add-var-multiple-example ... website: add example of multiple var cli	5 years ago
Pam Selle	ae52190c01	Merge pull request #27415 from techsolx/patch-1 ... Chage backend.tmpl to config.tmpl in Maps example,	5 years ago
Pam Selle	516ad2c8e4	Merge pull request #27432 from bulletinmybeard/patch-1 ... Update gcs.html.md	5 years ago
Pam Selle	e22ccd424c	Add note about removal to web docs	5 years ago
Cladius Fernando	25003a0caa	Corrected minor typo ... On Windows, the file must be named named terraform.rc => On Windows, the file must be named terraform.rc	5 years ago
Robin Schulz	64f9180a3c	Update gcs.html.md ... Just a typo	5 years ago
Chris Arcand	5440d9653b	[skip-ci] Remove documentation on 'CONFIRM_DESTROY' ... This variable mechanism was replaced long ago with a explicit `Allow destroy plans` setting on a Terraform Cloud workspace, and no longer does anything: https://www.terraform.io/docs/cloud/workspaces/settings.html#destruction-and-deletion Rather than mention this new mechanism at all though, I've removed the requisite from here entirely - the reason being that a consideration like this is no different from other permission concerns (e.g. "You must have Apply permission on a workspace to `apply`"), and without enumerating _all_ of these here - which doesn't seem appropriate - we just remove this concern entirely.	5 years ago
JohnM	72e657edcc	Chage backend.tmpl to config.tmpl in Maps example, ... Reference file in Maps example is named config.tmpl, example used backend.tmpl from previous section.	5 years ago
Nick Fagerlund	5ceb8b2b98	website: Adopt `terraform_remote_state` into language docs ... ...and also shrink the explanation for alternate sharing approaches, a bit. Actually, it looks like I already half-adopted it by accident. 😬 But this commit adds it to the sidebar under "State", so users can browse to it. I'm leaving the URL alone, because it's not urgent and we'll need to adjust a large swath of URLs at some point anyway. This change effectively stops presenting `terraform` as a provider in the normal sense, and reduces /docs/providers/terraform/index.html to a ghost page in the language section (to avoid breaking links for the time being). The message a reader should get is that Terraform has one special built-in data source where you don't need to think about the provider or its version.	5 years ago
stakiran	3ce7edc018	website: Fix wrong link of operators. ... not "references.html" but "operators.html".	5 years ago
Nick Fagerlund	cc6a226bcf	website: Remove provider category indexes, reduce main list ... As of December 18, 2020, we've redirected nearly all of the provider documentation that used to live on terraform.io: - For providers that got published on the Registry, we redirected each docs page to the corresponding Registry docs page. - For providers that never got adopted by a new publisher, we archived the GitHub repository and redirected each docs page to the corresponding Markdown source file on github.com. (For an example of these redirects, see https://www.terraform.io/docs/providers/telefonicaopencloud/r/s3_bucket.html) There are ten providers left that we haven't redirected. These ones got adopted by new publishers and _will_ end up on the Registry, but they aren't quite ready to ship and get their permanent redirects, and we don't want to sabotage their SEO by 301ing to a temporary destination.	5 years ago
Robin Norwood	235c141565	Add links to outputs and locals tutorials	5 years ago
Nick Fagerlund	85d477aee9	website: Fix numerous links with redirects or broken anchors ... These links largely still go somewhere useful, but they have some kind of issue revealed by our new link checker: - Some of them point to a stale URL that redirects, and can be updated to the new destination. - Some of them point to anchors that don't exist (anymore?) in the destination. - Some of them end up redirecting unnecessarily due to how the server handles directory URLs without trailing slashes. Sorry, I know that's pointless, just, humor me for the time being so we can get our CI green. 😭 In a couple cases, I've added invisible anchors to destination pages, either to preserve an old habit or because the current anchors kind of suck due to being particularly long or meandering.	5 years ago
Nick Fagerlund	1fff4e2690	website: Update links to redirected provider docs pages ... This commit intentionally leaves the indexes of provider docs alone, to avoid merge conflicts when we delete those.	5 years ago
Pam Selle	1970c14a53	[docs] Add limitations section to for_each (#27299) ... * Add limitations section to for_each Move limitations from a note to their own section, to allow for expansion on disallowing sensitive values in for_each	5 years ago
Pam Selle	d7f3239c51	Document sensitivity + function call behavior	5 years ago
Repon Kumar Roy	7d093cbede	website: add example of multiple var cli ... This PR updates the documentation of input variable of terraform. It's mentioned that multiple `-var` is possible, but no example is given. This PR adds an example of multiple `-var` option	5 years ago
Kristin Laemmert	8bab3dd374	command/state list: list resources in nested and expanded modules (#27268) ... * command/state list: list resources in nested and expaneded modules A few distinct bugs fixed in here: There was a bug in the logic checking if a given module was the child of the targetAddr, now fixed. That resolved the basic issue where resources in nested submodules were not listed. The logic around allowMissing needed some tweaking to allow for empty modules, as long as those modules had submodules with resources. state list is the only command using allowMissing with false so this felt safe to do. Finally I extended the logic so list would included expanded modules, which is to say giving module.foo would result in resources from module.foo[1], module.foo[0], etc. * update state list docs to show that module filtering includes any nested modules	5 years ago
James Bardin	cd4cb3f8d2	add implied data depends_on caveat	5 years ago
Martin Atkins	3268a7eaba	command/output: Raw output mode ... So far the output command has had a default output format intended for human consumption and a JSON output format intended for machine consumption. However, until Terraform v0.14 the default output format for primitive types happened to be _almost_ a raw string representation of the value, and so users started using that as a more convenient way to access primitive-typed output values from shell scripts, avoiding the need to also use a tool like "jq" to decode the JSON. Recognizing that primitive-typed output values are common and that processing them with shell scripts is common, this commit introduces a new -raw mode which is explicitly intended for that use-case, guaranteeing that the result will always be the direct result of a string conversion of the output value, or an error if no such conversion is possible. Our policy elsewhere in Terraform is that we always use JSON for machine-readable output. We adopted that policy because our other machine-readable output has typically been complex data structures rather than single primitive values. A special mode seems justified for output values because it is common for root module output values to be just strings, and so it's pragmatic to offer access to the raw value directly rather than requiring a round-trip through JSON.	5 years ago
Pam Selle	aa044bdd39	Fix docs for 0.15 for vendor provisioners	5 years ago
Hyunsuk Shin	16f8baa40e	Update setproduct.html.md (#27184) ... fill wrong syntax	5 years ago
Martin Atkins	776b33db32	website: Recommend against making JSON/YAML with heredocs ... This is a repeated cause of confusion and questions in the community forum, because both JSON and YAML valid syntax are hard to generate using just string concatenation. Terraform has built-in functions for both of these common serializations to avoid those problems, and so this will hopefully make these better alternatives more discoverable.	5 years ago
Martin Atkins	ab1dd87540	website: Elaborate the "expressions" sub-pages in the language section ... When we did the earlier documentation rework for Terraform v0.12 we still had one big "Expressions" page talking about the various operators and constructs, and so we had to be a bit economical with the details about some more complicated constructs in order to avoid the page becoming even more overwhelming. However, we've recently reorganized the language documentation again so that the expressions section is split across several separate pages, and that gives some freedom to go into some more detail about and show longer examples for certain features. My changes here are not intended to be an exhaustive rewrite but I did try to focus on some areas I've commonly seen questions about when helping in the community forum and elsewhere, and also to create a little more connectivity between the different content so readers can hopefully find what they are looking for more easily when they're not yet sure what terminology to look for.	5 years ago
Pam Selle	b963ea8594	Update docs and add warning for -get-plugins ... As of Terraform 0.13+, the get-plugins command has been superceded by new provider installation mechanisms, and general philosophy (providers are always installed, but the sources may be customized). Updat the init command to give users a warning if they are setting this flag, to encourage them to remove it from their workflow, and update relevant docs and docstrings as well	5 years ago
Pam Selle	0c0ea09546	Merge pull request #27134 from tillepille/patch-1 ... documentation: fix small typo	5 years ago
Dmitry Tokarev	8d1c416a53	website: Fix link to external documentation "Git URLs"	5 years ago
Masayuki Morita	93b6f15c9d	website: Fix typo in docs/commands/cli-config (#27038)	5 years ago
Nick Fagerlund	0c0749edcf	website: Fix several broken links (#27091)	5 years ago
Martin Atkins	323cd4364b	website: Correct formatting for lists in dependency lock docs ... I originally drafted these docs in a context where I was relying on GitHub's Markdown renderer, and carelessly imported them into the Terraform website without verifying that the website's Markdown renderer could process it. This particular quirk has bitten us before: the website Markdown parser expects follow-on paragraphs in a list item to be indented at least four spaces, and with less than that it ignores the leading whitespace altogether and just understands a normal paragraph. This change will cause the follow-on paragraphs to now correctly render as part of the bullet points they are intended to be attached to.	5 years ago
Mark Lewis	9935138e1c	Update for_each.html.md ... minor grammar improvement.	5 years ago
Mark Lewis	ffea7a4cda	Update for_each.html.md	5 years ago
Tim Schrumpf	e102465e91	fix small typo	5 years ago
Connor Osborn	2c2ed53ff3	Fix apt install typo (#27074) ... Apt install expects a `name=version` NOT `name==version`	5 years ago
Petros Kolyvas	5cb2d4894c	Anytrue alltrue docs clarification. (#27108) ... * Anytrue alltrue docs clarification. * Update alltrue.html.md I can't spell. * Update anytrue.html.md Yes, I can't spell.	5 years ago
Nick Fagerlund	cca1bc91c3	website: fix bad layout in defaults function page ... This layout no longer exists.	5 years ago
Nick Fagerlund	5cff04b3ab	website: fix malformed yaml in a few function pages	5 years ago
Pam Selle	c6ab9b1553	Merge pull request #26938 from hashicorp/pselle/remove-vendor-provisioners ... Remove vendor provisioners	5 years ago
Martin Atkins	832bd5f41f	website: Initial docs for the provider_sensitive_attrs experiment ... This is under a heading "Sensitive Resource Attributes" on the assumption that if we later stabilize this feature then this heading will live on with some different content that describes the propagation of sensitive values from resource attributes, rather than describing the experiment.	5 years ago
Pam Selle	67fe3bfd69	Merge pull request #27058 from hashicorp/paultyng-patch-1 ... Add comments about this URL being linked to in the CLI	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	d5950b7fd2	website: link to dependency lock file tutorial	5 years ago
Nick Fagerlund	652b48bb49	website: link to sensitive variables tutorial	5 years ago
Nick Fagerlund	a1e73ade61	website: link to expressions tutorial where applicable ... This tutorial uses references to local values, conditional expressions, and splat expressions, so I've added it to those pages as well as the expressions overview.	5 years ago
Nick Fagerlund	5895472c93	website: link to functions tutorial where applicable	5 years ago
Paul Tyng	c4b46a5c98	Update signing.html.md	5 years ago
Martin Atkins	111825da45	website: More words about "terraform fmt" ... We've historically made statements like this in response to requests for more customization to the "terraform fmt" behavior, but the documentation itself was somewhat vague about the intended goals of this command. This is an attempt to be more explicit that consistency between codebases is the primary goal of this command, and that the examples in the Terraform documentation are our main guide for what is "idiomatic style" when adding additional rules over time. Nothing here is intended to be new policy, but instead as codifying positions we've taken elsewhere in the past in the hope of allowing users to decide how (and whether) they wish to make use of this tool.	5 years ago
Alisdair McDiarmid	42437482e5	Merge pull request #26947 from hashicorp/alisdair/backend-validate-remote-backend-terraform-version ... backend: Validate remote backend Terraform version	5 years ago
Alisdair McDiarmid	c5c1f31db3	backend: Validate remote backend Terraform version ... When using the enhanced remote backend, a subset of all Terraform operations are supported. Of these, only plan and apply can be executed on the remote infrastructure (e.g. Terraform Cloud). Other operations run locally and use the remote backend for state storage. This causes problems when the local version of Terraform does not match the configured version from the remote workspace. If the two versions are incompatible, an `import` or `state mv` operation can cause the remote workspace to be unusable until a manual fix is applied. To prevent this from happening accidentally, this commit introduces a check that the local Terraform version and the configured remote workspace Terraform version are compatible. This check is skipped for commands which do not write state, and can also be disabled by the use of a new command-line flag, `-ignore-remote-version`. Terraform version compatibility is defined as: - For all releases before 0.14.0, local must exactly equal remote, as two different versions cannot share state; - 0.14.0 to 1.0.x are compatible, as we will not change the state version number until at least Terraform 1.1.0; - Versions after 1.1.0 must have the same major and minor versions, as we will not change the state version number in a patch release. If the two versions are incompatible, a diagnostic is displayed, advising that the error can be suppressed with `-ignore-remote-version`. When this flag is used, the diagnostic is still displayed, but as a warning instead of an error. Commands which will not write state can assert this fact by calling the helper `meta.ignoreRemoteBackendVersionConflict`, which will disable the checks. Those which can write state should instead call the helper `meta.remoteBackendVersionCheck`, which will return diagnostics for display. In addition to these explicit paths for managing the version check, we have an implicit check in the remote backend's state manager initialization method. Both of the above helpers will disable this check. This fallback is in place to ensure that future code paths which access state cannot accidentally skip the remote version check.	5 years ago