terraform

Commit Graph

Author	SHA1	Message	Date
James Bardin	e40727076f	Update website/docs/language/modules/develop/providers.html.md Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	9859d4e70b	Update website/docs/language/modules/develop/providers.html.md Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
James Bardin	dfd8424392	link configuration aliases between pages	5 years ago
James Bardin	1bb602859a	update docs for configuration_aliases Remove references to the "proxy configuration block" concept, and add examples showing the usage of `configuration_aliases`.	5 years ago
Stephen	e39abbf6f0	fix regex logical or documentation (#27637 ) * fix regex logical or documentation Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
Robin Norwood	181048b913	Add crosslink to new Learn tutorial	5 years ago
Alisdair McDiarmid	888f36aebb	cli: Remove positional plan argument from graph To make the command arguments easier to understand and extend, we are moving away from positional arguments. This commit changes the graph command to take a `-plan` flag instead of an optional trailing path.	5 years ago
Pam Selle	6da55c0521	Update grammar for flags	5 years ago
Andor Markus	f658531883	Updating terraform workspace website list.html.md new.html.md select.html.md files thus it reflect the current version of Terraform CLI	5 years ago
Pam Selle	e1b0e3ce92	Remove -module option for taint and untaint This has been an error with help text, and can be removed.	5 years ago
Alisdair McDiarmid	75d38b50b1	docs: Note: state pull upgrades to current version	5 years ago
Nick Fagerlund	6d016af7c5	website: Remove links to legacy provider docs for GitHub, ksyun These providers are now published to the registry, as planned.	5 years ago
Nick Fagerlund	4e4f6b3f42	website: Restore note about standard vs. enhanced backends	5 years ago
Nick Fagerlund	33d2d9abb5	website: CLI: Remove several ghost pages, update old links - /docs/plugins/* - /docs/commands/state/addressing.html These were redundant pages.	5 years ago
Nick Fagerlund	d1e8537b33	website: CLI: Update links to moved docs pages	5 years ago
Nick Fagerlund	a8332703c9	website: CLI: Move docs files to match new URLs	5 years ago
Nick Fagerlund	b909a4a3a1	website: Move hidden attr-as-blocks page into new URL structure This is a "ghost page" that remains relevant and useful, under certain rare circumstances.	5 years ago
Nick Fagerlund	8cfcd82be3	website: Language: Remove several ghost pages, update links During the language/CLI docs reorg, we noticed several pages that were no longer viable; some were redundant, some useless, and some just very obsolete. Since we were trying to avoid breaking links at the time, we opted to remove them from the navs and leave them as "ghost pages" — still accessible, but not findable. This commit finally cleans these ghosts up and updates any remaining links to relevant modern pages. Bustin' makes me feel good. 👻🚫	5 years ago
Nick Fagerlund	7a8dd326c6	website: Language: Update links to moved pages	5 years ago
Nick Fagerlund	78dcc8dc1b	website: Language: Move files to match new URL structure	5 years ago
Nick Fagerlund	22d7c11d8a	website: Language: Remove the "this is 0.12+" message from language docs The sun has set on 0.11, so the value of maintaining this message on nearly every page has crashed to almost zero. Time to pull it.	5 years ago
fredtrimble	7b3b401da4	Update index.html.md Change the word "date" to "data"	5 years ago
Pam Selle	61f9d2177b	Merge pull request #27486 from hashicorp/pselle/version-doc Add documentation page for version	5 years ago
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
Nick Fagerlund	66f2c82d33	website: Add version command to sidebar nav and to plugins overview page	5 years ago
Pam Selle	cf0c54f834	Add documentation page for version The version command, although not the mightiest of our commands, did not have a page among our docs.	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.	6 years ago
Nick Fagerlund	2014e8ef64	website: Remove registry docs (adopted into terraform-website) The Registry is a web service whose behavior isn't directly tied to Terraform core's release cycle; therefore, its docs should be decoupled from that release cycle as well. https://github.com/hashicorp/terraform-website/pull/1517 adopts the registry docs into hashicorp/terraform-website, which already hosts several other corpuses of documentation that aren't tied to Terraform core's version (like Terraform Cloud, Terraform Enterprise, and Extending Terraform). Once that PR is merged, we should remove the registry docs from this repository to avoid confusing anyone.	6 years ago
Nick Fagerlund	db82b80c9d	website: Fix a random typo in azurerm backend	6 years ago
Nick Fagerlund	f2f47c3c9f	website: Fix title of `terraform providers lock` page (#26956 ) Probably a copy/paste error. Co-authored-by: Petros Kolyvas <petros@hashicorp.com>	6 years ago
Martin Atkins	af3f78975e	website: Fix confusing example for local-exec provisioner The local-exec provisioner documentation includes an example which refers to an attribute of the current resource using its full traversal path, rather than using "self" as we typically expect. Due to some coincidences in how Terraform builds the dependency graph, referring to the resource in this way happens to work when the resource has only a single instance (the graph builder just skips that self-referential dependency edge), but it fails if the user later tries to add "count" or "for_each" to the resource, because at that point all of the instances become dependent on one another, which creates a dependency cycle. Using "self" to access the current instance attributes is the usual approach, so I've updated the documentation to show that.	6 years ago
Martin Atkins	9f45a73581	website: Reword confusing statement about module sources in TFE As written previously this seemed to suggest using "app.terraform.io" (the "hostname you use to access the Terraform Cloud application) to access a private registry in Terraform Enterprise, but that isn't true and I assume isn't what was intended. Instead, the hostname for a Terraform Enterprise instance is the hostname where the Terraform Enterprise application is running, which is both the hostname where users would find its web UI and the hostname they'd use to configure the "remote" backend for remote operations and state storage.	6 years ago
Martin Atkins	df47da1f8e	website: "coalesce" function unifies its argument types In order to be able to predict a result type even if arguments are not yet known, coalesce requires all of its arguments to be of the same type. Our usual automatic conversion rules mean that in some cases the result is a silent type conversion rather than an explicit error, so we'll at least document that so that folks who encounter it can understand what is causing the likely-surprising behavior. If we were building this function over again today I expect we'd make it always return an error under type mismatch, but to do so now would be a breaking change and the potential cost of that seems too high for something that doesn't seem to arise incredibly often in practice.	6 years ago
Nick Fagerlund	2bfec75bbf	website: Update all links to {expressions,modules,resources}.html ...as well as to the standard module structure section in module development.	6 years ago
Nick Fagerlund	209541aaf0	website: Break up main Modules and Module Development pages This one is a lot like the previous two commits, but slightly more complex: - Only adding one new meta-argument page, for `providers`; otherwise, it just re-uses the dual-purpose pages I made in the resources commit. - About that `providers` argument: The stuff that was relevant to consumers of a module went in that meta-argument page, but there was also a huge deep dive on how the _author_ of a re-usable module should handle provider configurations in cases where inheriting the default providers isn't sufficient. THAT, I moved into a new page in the module development section. (For the consumer of a module, this should all be an implementation detail; the module README should tell you which aliased providers you need to configure and pass, and then you just do it, without worrying about proxy configuration blocks etc.) - The "standard module structure" recommendations in the main module development page gets a page of its own, to make it more prominent and discoverable. - Same deal with using the old URL as a landing page, at least for the main module calls page. It didn't seem necessary for the module development page.	6 years ago
Nick Fagerlund	6e2f5eb0be	website: Break up Resources page into smaller chunks - Resource behavior gets its own page. - Meta-arguments all get their own pages. - Stuff about resource syntax itself gets a page. In the process of breaking the meta-arguments out into their own pages, I revised them (with the exception of `provider`) so that they apply to both resources and modules. Like with Expressions, this commit repurposes the old resources.html URL as a landing page for old links.	6 years ago
Nick Fagerlund	a446ecb7b7	website: Break up Expressions page into smaller chunks This commit converts the previous URL for this content to a landing page, which captures all of the previous in-page anchors and directs readers to the new home for each section.	6 years ago
Martin Atkins	6bb9fa7341	website: Document alternatives to terraform_remote_state For some time now we've been recommending explicitly passing data between configurations using separate resource types and data sources, rather than always using terraform_remote_state, for reasons including reducing coupling between subsystems and allowing a configuration's state snapshots to be under restrictive access controls. However, those recommendations have so far not appeared directly in the documentation for terraform_remote_state, and have instead just been alluded to elsewhere in the documentation when discussing ways to pass data between configurations. This change, then, is an attempt to be clear and explicit about the recommendation and to give a variety of specific examples of how to implement it. The terraform_remote_state data source page is admittedly not the most obvious place in the information architecture to put a set of alternatives to it, but it does appear that this documentation page is where people most commonly end up when researching options in this area and so I've put this here in an attempt to "meet people where they are". Possibly in a future documentation reorganization we might have an separate page specifically about sharing data between configurations, but we don't currently have time to do that bigger reorganization. If we do so later, the content on this page could potentially be replaced with a summary of the recommendation and a link to another place for the details, but the goal here is to make this information visible in the existing location people look for it, rather than blocking until there's a better place for it to live. This also includes a small amount of editing of some existing content on the page to use terminology and style more similar to how our main configuration language documentation is written,.	6 years ago
Pam Selle	e39e0e3d04	Remove vendor provisioners and add fmt Make target Remove chef, habitat, puppet, and salt-masterless provsioners, which follows their deprecation. Update the documentatin for these provisioners to clarify that they have been removed from later versions of Terraform. Adds the fmt Make target back and updates fmtcheck script for correctness.	6 years ago
Martin Atkins	7ccaee1018	website: Fix inconsistencies in the registry protocol page Some hasty, incorrect merge conflict fixing caused this page to have a strange mix of terminology between "system" and "provider". Along with that, there were also several editorial errors caused by text on this page having originally been derived from the provider registry documentation. This documentation will now consistently talk about being a module registry protocol rather than a provider registry protocol, and it will consistently use the term "system" as a generic term for the final part of the module source address, aside from noting that there is an optional convention to name it after the "type" part of an official provider when possible.	6 years ago
Andrew Fitzgerald	8c82b3f6a0	Remove 'system' references from module registry protocol docs.	6 years ago
TEDmk	8195a99529	Add a missing new line The missing new line doesn't permit the code block to show up.	6 years ago
Martin Atkins	cec4578005	lang/funcs: Experimental "defaults" function This is a new part of the existing module_variable_optional_attrs experiment, because it's intended to complement the ability to declare an input variable whose type constraint is an object type with optional attributes. Module authors can use this to replace null values (that were either explicitly set or implied by attribute omission) with other non-null values of the same type. This function is a bit more type-fussy than our functions typically are because it's intended for use primarily with input variables that have fully-specified type constraints, and thus it uses that type information to help inform how the defaults data structure should be interpreted. Other uses of this function will probably be harder today because it takes a lot of extra annotation to build a value of a specific type if it isn't passing through a variable type constraint. Perhaps later language features for more general type conversion will make this more applicable, but for now the more general form of this problem is better solved other ways.	6 years ago
Pam Selle	9f5f5adc0d	Merge pull request #26799 from flatiron32/patch-1 Remove redundant Local Named Values section	6 years ago
Kent 'picat' Gruber	63cc597bc3	Fix grammar Co-authored-by: Pam Selle <pam@hashicorp.com>	6 years ago
Kent 'picat' Gruber	20026819dd	Remove path-style specific wording in module sources doc Follow up on wording added in https://github.com/hashicorp/terraform/pull/20377	6 years ago
hhofs	5b99a56fde	communicator/ssh: Add support for Windows targets (#26865 )	6 years ago
Nick Fagerlund	5e18e44037	Merge pull request #26723 from hashicorp/oct20_language_and_cli_docs website: TF-153: Split core Terraform docs into "Language" and "CLI"	6 years ago
Nick Fagerlund	2c02233a16	website: Add new "glue"/overview pages for CLI and language docs The new nav structure demanded a few new pages that give context about a feature or workflow. In a few cases, they take text from an existing page. Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> Co-authored-by: Judith Malnick <judith.patudith@gmail.com>	6 years ago
Martin Atkins	80b13307e8	website: Initial docs about the APT/Yum repositories The HashiCorp engineering services team has set up APT and Yum repositories as alternative installation methods for various HashiCorp products, now including Terraform. We don't really have a great place to talk about these in our current website structure. There is a longer-term plan to revamp the downloads page to include other options, but we are already getting lots of questions about how to use these repositories and so my goal here is to publish at least a first pass of documentation, linked from the Downloads page sidebar as a placeholder for now, so we'll have somewhere to refer to when answering such questions. My intent is that even once we have a revamped Downloads page that mentions these options more clearly, we'll still need to link out to another page to talk about various details, and so the two new URLs this creates would be the home of that content, even if we rewrite the specific prose here to work better in the context of the new Downloads page.	6 years ago
Andor Markus	9d3143381b	Update delete.html.md (#26874 )	6 years ago
Justin Campbell	7c98be92c2	website: Add Registry docs for webhooks (#26870 )	6 years ago
Robin Norwood	ec7d9c85ac	Update link to new varibles tutorial	6 years ago
Upo	3b9c5e5bbb	backend/gcs: remove deprecated "path" config argument (#26841 )	6 years ago
Alisdair McDiarmid	3680bc521a	website: Update output command docs The example configuration now uses Terraform 0.12+ syntax, and the output examples are up to date with the current text UI. We also add an explicit recommendation to use the `-json` option for a consistent and stable output format, for use in automation.	6 years ago
Upo	4ccc63d79d	backend: Add service account impersonation to GCS Backend and update the docs (#26700 )	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
Tej-Singh-Rana	832918c65b	website: fixed spelling error (#26758 )	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
alevinetx	66393bb62e	website: Update module-registry-protocol.html.md (#26639 ) * Update module-registry-protocol.html.md 1: There is a mismatch in the segment labels for the version query URL (system vs provider) 2: There is a discrepancy between the documentation and the actual generated request for retrieving module source code (URL segments 4 vs 3) - There is no segment for "provider" * Update module-registry-protocol.html.md Changed ```:system``` to ```:provider``` for versions and source API URLs	6 years ago
Nick Fagerlund	4cc9585fee	website: Rename registry docs to "Publishing Providers & Modules" Also, remove redundant sidebar_current noise from sidebar nav source.	6 years ago
Nick Fagerlund	8657b6d51c	website: Make most of /docs/plugins into ghost pages on Extend These pages are thoroughly obsolete. Later, we'll delete and redirect them; for now, we'll make sure the relevant pages are front-and-center in the sidebar if someone somehow ends up on here.	6 years ago
Nick Fagerlund	fa9ad0c5e5	website: Adopt islanded subcommands into unified "docs" (CLI) layout Several `terraform` subcommands include sub-sub-commands; with our old sidebar system, viewing those took you to an isolated "island" nav sidebar, away from the main docs. The new navigation will adopt all these pages, so we don't need to exile the reader to odd places.	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
Martin Atkins	6a44586a8f	website: Update the CLI commands index page for latest help output My initial motivation here was to update the example output from Terraform's top-level help list to match recent updates in the layout and language used. However, while here I took the opportunity to update some dated language that was not consistent with our modern documentation writing style, in particular including a totally unnecessary and potentially-alienating claim that Terraform is "very easy to use". Our modern writing style discourages this sort of "boastful" language and encourages us to focus on the facts at hand.	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
James Bardin	ff94be21c2	Merge pull request #26685 from hashicorp/jbardin/separate-loggers Separate loggers	6 years ago
James Bardin	eb2d4434c8	logging env variable docs	6 years ago
Petros Kolyvas	bfbdbe9bba	Tool-specific provisioner docs change to red notice box (#26681 )	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
Jakson Rodrigues	818029826b	Fixed config argument on example (#26304 )	6 years ago
Kerim Satirli	f4790d8f61	updates `description` to reflect endpoint usage (#26278 )	6 years ago
Thanonchai	f3fa59f65d	Update config.html.md (#26622 ) * Update config.html.md When reading this page, I couldn't find the list of the "supported backends to the left". They're actually on a different page, so thought I'd update it so that others wouldn't find it confusing like me. If this is ok with you, would it be possible to label this PR with 'hacktoberfest-accepted'? I'm still new to this. If not, I'd be alright. Thank you! * Update config.html.md Swapped the full URL in the link for a relative path Co-authored-by: Petros Kolyvas <petros@hashicorp.com>	6 years ago
Justin Long	0ce11faffd	Clear wording that bucket must pre-exist (#26276 ) Experienced similar issue as https://github.com/hashicorp/terraform/issues/18417 this updates the documentation so that it's more clear a storage bucket must exist prior to configuring the backend.	6 years ago
Jerry Chong	2f091836c9	Modified terraform get command (#26465 ) -Added PATH -Added -no-color option	6 years ago
Diod FR	f0edb192b3	ADD CLI option position for force-unlock command (#26626 ) * ADD CLI option position for force-unlock command * Update force-unlock.html.markdown Made a change to also include the missing [DIR] Co-authored-by: Petros Kolyvas <petros@hashicorp.com>	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
Alisdair McDiarmid	5e047b0a0b	Merge pull request #26611 from hashicorp/alisdair/sensitive-values-provisioners Fixes for sensitive values used as input to provisioners	6 years ago
Alisdair McDiarmid	9d2994ab9b	website: Sensitive values in provisioner config	6 years ago
Pam Selle	02c48f8071	Comment fixing	6 years ago
Martin Atkins	30204ecded	command/cliconfig: Allow development overrides for providers For normal provider installation we want to associate each provider with a selected version number and find a suitable package for that version that conforms to the official hashes for that release. Those requirements are very onerous for a provider developer currently testing a not-yet-released build, though. To allow for that case this new CLI configuration feature allows overriding specific providers to refer to give local filesystem directories. Any provider overridden in this way is not subject to the usual restrictions about selected versions or checksum conformance, and activating an override won't cause any changes to the selections recorded in the lock file because it's intended to be a temporary setting for one developer only. This is, in a sense, a spiritual successor of an old capability we had to override specific plugins in the CLI configuration file. There were some vestiges of that left in the main package and CLI config package but nothing has actually been honoring them for several versions now and so this commit removes them to avoid confusion with the new mechanism.	6 years ago
Tony Carmichael	9ff007d322	Update community-index.html.markdown	6 years ago
Tony Carmichael	49a3d14b3b	Update community-index.html.markdown Updates to community listings now that registry has been GA for a few months.	6 years ago
James Bardin	ffbdd72196	Merge pull request #26487 from hashicorp/jbardin/shell-escape update taint command example	6 years ago
James Bardin	657dd33008	Merge pull request #26557 from remilapeyre/skip-ddl-commands Add skip_table_creation and skip_index_creation options to the pg backend	6 years ago
Pam Selle	8f72f4f317	Merge pull request #21936 from tiny-dancer/patch-1 Terraform Plan CLI Vars Format	6 years ago
Pam Selle	305c6fc029	Merge branch 'master' into patch-2	6 years ago
Rémi Lapeyre	12a0a21c0b	Add skip_table_creation and skip_index_creation options to the pg backend Closes https://github.com/hashicorp/terraform/issues/25708	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
James Bardin	c1efe351b2	update taint command example Fix the example to match the usual shell style, and add a note about different shells requiring different escaping formats.	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
Jerry Chong	90cbc5a123	Modified terraform force-unlock command -Added code block for terraform force-unlock LOCK_ID	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
Thanonchai	85e83608fc	website: fix broken link to local backend in apply.html (#26307 ) The link to local backend doesn't exist. Update to what I believe is the correct one.	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
Robin Norwood	7ccea30b28	website: Terraform import and remote backends (#26241 ) * Put link to tutorial in its own section, call it a tutorial instead of guide, and use new canonical URL. * Mention limitations of using import with a remote backed * Typo fix Co-authored-by: Nick Fagerlund <nick.fagerlund@gmail.com>	6 years ago
Pam Selle	9c16724221	Merge pull request #26337 from hashicorp/pselle/docs-vendor-provisioners docs: Vendor provisioner deprecation version	6 years ago
Pam Selle	3ba38f9b1f	(docs) Vendor provisioner deprecation version	6 years ago
Justin Campbell	1554e04108	website: Add Registry email to publishing doc (#26327 )	6 years ago
Paul Tyng	59e77685cb	Merge pull request #26326 from hashicorp/paultyng-patch-1 Minor instructions update for GPG key creation	6 years ago
Justin Campbell	45666f8216	website: Update Registry key management docs (#26299 )	6 years ago
Paul Tyng	192c4337c3	Update publishing.html.md	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
Alisdair McDiarmid	3c6239f4c5	Merge pull request #26244 from hashicorp/alisdair/credentials-helper-no-credentials website: Credentials helper response for no creds	6 years ago
Pam Selle	81a6cde3cf	Merge pull request #26203 from hashicorp/pselle/deprecate-vendor-provisioners Deprecate vendor (3rd party) provisioners	6 years ago
Alisdair McDiarmid	aa8c73cd18	website: Credentials helper response for no creds For a credentials helper plugin to be useful with Terraform 0.13+, we need to cope with the case of having no credentials for a host without this being an error. This is to allow the public Terraform Registry to be accessed without supplying a token. The way to implement this is to respond to queries for credentials for a host which has no credentials stored with an empty object and a success exit code. This contradicts the previous documentation, which calls for an error response in this case.	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
Alisdair McDiarmid	7086e23bea	Merge pull request #26181 from hashicorp/alisdair/cli-config-implied-local-mirror-directories website: Fix docs for implied provider FS mirrors	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
Petros Kolyvas	0babd493ae	website: Add Google and Microsoft products to the summary for supported remote backends (#26204 ) * Added Google and Microsoft products to the summary for supported remote backends * Backends ordering change	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
Alisdair McDiarmid	3419422891	website: Fix docs for implied provider FS mirrors In addition to the directories previously listed, Terraform looks in the CLI config directory ($HOME/.terraform.d/plugins on macOS/Linux/UNIX, and %APPDATA%/terraform.d/plugins on Windows). List this in the documentation for clarity. We also add a note about the working directory relative "vendor" location, ./terraform.d/plugins.	6 years ago
Pam Selle	5153ea633b	Add docs notes for deprecation	6 years ago
Pam Selle	e191a57093	Merge pull request #25952 from shaowenchen/improvement_docs improvement github token	6 years ago
Pam Selle	5ec1868419	Merge pull request #25864 from alexnovak/patch-1 Correct annotation in expressions.html	6 years ago
Pam Selle	11119e7e3f	Merge pull request #26158 from fourplusone/patch-1 Fix broken link in providers/mirror documentation	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
Matthias Bartelmeß	cec5222287	Correct typo	6 years ago
Martin Atkins	efe78b2910	main: new global option -chdir This new option is intended to address the previous inconsistencies where some older subcommands supported partially changing the target directory (where Terraform would use the new directory inconsistently) where newer commands did not support that override at all. Instead, now Terraform will accept a -chdir command at the start of the command line (before the subcommand) and will interpret it as a request to direct all actions that would normally be taken in the current working directory into the target directory instead. This is similar to options offered by some other similar tools, such as the -C option in "make". The new option is only accepted at the start of the command line (before the subcommand) as a way to reflect that it is a global command (not specific to a particular subcommand) and that it takes effect _before_ executing the subcommand. This also means it'll be forced to appear before any other command-specific arguments that take file paths, which hopefully communicates that those other arguments are interpreted relative to the overridden path. As a measure of pragmatism for existing uses, the path.cwd object in the Terraform language will continue to return the _original_ working directory (ignoring -chdir), in case that is important in some exceptional workflows. The path.root object gives the root module directory, which will always match the overriden working directory unless the user simultaneously uses one of the legacy directory override arguments, which is not a pattern we intend to support in the long run. As a first step down the deprecation path, this commit adjusts the documentation to de-emphasize the inconsistent old command line arguments, including specific guidance on what to use instead for the main three workflow commands, but all of those options remain supported in the same way as they were before. In a later commit we'll make those arguments produce a visible deprecation warning in Terraform's output, and then in an even later commit we'll remove them entirely so that -chdir is the single supported way to run Terraform from a directory other than the one containing the root module configuration.	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
Petros Kolyvas	fa4917172d	Small typo in the internals link to the provider network mirror protocol page (#26098 )	6 years ago
Matt Kasa	c2e35ae3b5	backend/http: add support for configuration by environment variable (#25439 )	6 years ago
Justin Campbell	24f20177ee	website: Omitunnecessary instruction fror Registry The GitHub Action passes this in already.	6 years ago
Paul Tyng	0fae10a886	Add GitHub action instructions to publishing (#26076 ) Co-authored-by: Justin Campbell <justin@justincampbell.me>	6 years ago
Jai Govindani	d8b36e5d12	style(providers): update syntax for terraform >= 0.11	6 years ago
Nick Fagerlund	f57861936c	website: fix a broken community provider link	6 years ago
Tony Carmichael	d7de46df10	Update publishing.html.md docs updates for GPG key gen instructions	6 years ago
Pam Selle	f2d213c461	Merge pull request #25657 from pdecat/typo_hierarchical Typo: heirarchical => hierarchical	6 years ago
Kristin Laemmert	3e1f741666	webside/docs: add note re: archive subdirectories to http download (#26020 ) section	6 years ago
Pam Selle	ba461fe0e1	Merge pull request #26004 from bzeitler69/patch-1 chore: Update mirror.html.md	6 years ago
Roger Berlind	3070f21241	Fix foreach to for_each `foreach` on modules should be `for_each`	6 years ago
Martin Atkins	2bd2a9a923	internal/getproviders: HTTPMirrorSource implementation We previously had this just stubbed out because it was a stretch goal for the v0.13.0 release and it ultimately didn't make it in. Here we fill out the existing stub -- with a minor change to its interface so it can access credentials -- with a client implementation that is compatible with the directory structure produced by the "terraform providers mirror" subcommand, were the result to be published on a static file server.	6 years ago
Kristin Laemmert	4569a37de4	website/docs: provider source related clarifications	6 years ago
Bogdan Tsaitler	b738da2f04	Update mirror.html.md	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
Paul Tyng	7a34d4d709	Add Terraform Cloud provider requirements (#25991 )	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
shaowenchen	a2b52c0dfc	improvement github token Signed-off-by: shaowenchen <mail@chenshaowen.com>	6 years ago
Kristin Laemmert	9168abc3e5	website/docs: clarify behavior of -state flag (#25928 ) * website: clarify behavior of -state option	6 years ago
Rachel Sharp	f44d32ab57	update cloud-init casing	6 years ago
Rachel Sharp	bb598c27fe	Updating links for cloud init guide in docs	6 years ago
James Bardin	d46e9a4198	Merge pull request #25770 from hashicorp/f/azure-backend-spcert backend/azurerm: support for authenticating using a Client Certificate	6 years ago
Angie Pinilla	582fb73a7c	deps: Update aws-sdk-go-based to 0.6.0	6 years ago
Alex Novak	82aa2d4467	Correct annotation in expressions.html `false` section was missing a finishing "`"	6 years ago
Tony Carmichael	76fb0515af	Update publishing.html.md Clarify steps for sending in GPG keys if publishing with a GH org.	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
Petros Kolyvas	30c50a3b33	Small docs fix for broken link	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	7bc75a1804	website: Edits to updated Registry documentation - Edits to registry overview - Add index link as 'overview' (header links are semi-invisible) - move providers/overview.html to providers/index.html - Edits to providers overview - fix filename of os-arch - edits to provider publishing	6 years ago
Tony Carmichael	cde98a3172	website: Update Registry documentation for Terraform 0.13 release Co-authored-by: Tom Bamford <tbamford@hashicorp.com>	6 years ago
tombuildsstuff	0d34e5d97c	backend/azurerm: support for authenticating using a Client Certificate fixes #24179 supersedes #19606 dependent on #25769	6 years ago
Martin Atkins	08ba58c8c8	website: Documentation about the one-to-one object binding assumption Terraform's design assumes that each remote object in Terraform's care is bound to one resource instance and one alone. If the same object is bound to multiple instances then confusing behavior will often result, such as two resource configurations competing to update a single object, or objects being "left behind" when all existing Terraform deployments are destroyed. This assumption was previously only implied, though. This change is an attempt to be more explicit about it, although these are additions to some older documentation sections that have not been revised for some time and so this is just a best effort to make this information discoverable without getting drawn into a full-on reorganization of these sections. While revising this there were some particular oddities that I decided to revise while I was there, but I'll leave a fuller revision of this older content for a later commit when we have more time to review it in greater detail.	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
Paul Tyng	5fea948cc6	Merge pull request #25676 from hashicorp/website-registry-docs-subcategory-sorting website: Registry docs nav sorts some subcategies	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
Justin Campbell	0ca0014c56	website: Registry docs nav sorts some subcategies	6 years ago
Petros Kolyvas	c2d6276238	Merge pull request #25076 from iTEx-aaa/patch-1 Update index.html.markdown (removing quotes from keywords in provisioner docs)	6 years ago
Patrick Decat	062865735f	Typo: heirarchical => hierarchical	6 years ago
MorganGeek	3b6c1ef156	Fix spelling mistakes/typos in documentation	6 years ago
Tony Carmichael	e935719f46	Update publishing.html.md Fix callout formatting as it was not displaying correctly.	6 years ago
Paul Tyng	62016849dd	Add link to os/arch page	6 years ago
Paul Tyng	19265fe4b0	Add recommend os/arch page	6 years ago
Justin Campbell	24064c4ed9	website: Add links to registry doc preview tool (#25619 )	6 years ago
Shunsuke Suzuki	1dd4d70bab	docs: fix the output format of state show command From v0.12 the output format of state show command seems to be changed but the old format is used in the document.	6 years ago
Tony Carmichael	e320cd2b35	website: fix markdown formatting in publishing.html.md (#25598 )	6 years ago

... 3 4 5 6 7 ...

1454 Commits (dc0dd75b602fef76d55a67f0aab0eb7016b995ce)