142 Commits (277fe647b95e32b9ca0738cd20af09735954dfd8)

Author	SHA1	Message	Date
Laura Pacilio	07accd7a38	Add page metadata to variables and outputs overview	5 years ago
Laura Pacilio	9dc008fa10	Add metadata description to dependency lock file page	5 years ago
Laura Pacilio	62b11f02e2	Make metadata description more concise	5 years ago
Laura Pacilio	62b444504d	Add description metadata to provider requirements	5 years ago
Laura Pacilio	d107b46270	Make description metadata more concise	5 years ago
Laura Pacilio	bca3957e17	Update description metadata for input variables	5 years ago
Laura Pacilio	134170c121	Fixing broken link on syntax page	5 years ago
Laura Pacilio	f5c463c27e	Update broken link oon provisioners connection page	5 years ago
Laura Pacilio	493d4b8dc8	Update description metadata	5 years ago
Laura Pacilio	f25d993b47	Update description metadata to include key words	5 years ago
Laura Pacilio	6f8774a8ed	Add Terraform to description metadata for SEO	5 years ago
Laura Pacilio	2e25fd04c0	Add description metadata to provisioners index page	5 years ago
Laura Pacilio	6d0569ac45	Add description metadata to lifecycle page	5 years ago
Laura Pacilio	66103f273e	Add description metadata to resource provider page	5 years ago
Laura Pacilio	96994d0b01	Add description metadata to for_each page	5 years ago
Laura Pacilio	4a2a6e8b52	Add description metadata to count and update depends_on	5 years ago
Laura Pacilio	ddabca8c72	Add description metadata to depends_on page	5 years ago
Laura Pacilio	e60e77c68f	Add description metadata to behavior page	5 years ago
Laura Pacilio	66dfb56d4f	Update description metadata to include key words	5 years ago
Laura Pacilio	810543b997	Add description metadata to resources overview page	5 years ago
Laura Pacilio	08f1d6c9e0	Update description metadata for style page	5 years ago
Laura Pacilio	c33970bfa4	Add description metadata to JSON syntax page	5 years ago
Laura Pacilio	5384aacb5e	Update description metadata for key words	5 years ago
Laura Pacilio	887b019761	Fix capitalization on Terraform language	5 years ago
Laura Pacilio	a62e2825c7	Add description metadata to syntax overview	5 years ago
Laura Pacilio	f6b500379d	Update description metadata to include Terraform key word	5 years ago
Laura Pacilio	ab06843f1d	Add description metadata to files and directories	5 years ago
Laura Pacilio	8525befc22	Add description metadata to index page	5 years ago
Laura Pacilio	577c3653f2	Merge pull request #28983 from KurtLehnardt/patch-1 ... fixed typo	5 years ago
Laura Pacilio	de97a03528	Merge pull request #28908 from kondr57/patch-1 ... fix typo	5 years ago
Martin Atkins	a945b379d8	website: Explicit examples of -var escaping in various shells ... The -var command line option comes with the disadvantage that a user must contend both with Terraform's own parser and with the parser in whichever shell they've decided to use, and different shells on different platforms have different rules. Previously we've largely just assumed that folks know the appropriate syntax for the shell they chose, but it seems that command lines involving spaces and other special characters arise rarely enough in other commands that Terraform is often the first time someone needs to learn the appropriate syntax for their shell. We can't possibly capture all of the details of all shells in our docs, because that's far outside of our own scope, but hopefully this new section will go some way to give some real examples that will help folks figure out how to write suitable escape sequences, if they choose to set complex variable values on the command line rather than in .tfvars as we recommend elsewhere on this page.	5 years ago
Robin Norwood	50fe980877	Merge pull request #28998 from hashicorp/rln-add-versions-tutorials-links ... Add links to terraform versions tutorials	5 years ago
Robin Norwood	2c71bb3a2e	Add links to terraform versions tutorials	5 years ago
Radek Simko	bb868606ea	docs: Document naming conventions for templates & backend configs (#28924) ... * docs: Document naming conventions for templates & backend configs * Update website/docs/cli/config/config-file.html.md Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com> * Update website/docs/language/functions/templatefile.html.md Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com> Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>	5 years ago
Kurt Lehnardt	165b2a2509	fixed typo	5 years ago
Kristin Laemmert	9ca3cb4233	website/docs: move type func docs to a useful location (#28940) ... * website/docs: move type func docs to a useful location * docs don't exist if you don't put them in the index (again)	5 years ago
Vladimir Kondratiev	58a5207dc4	fix typo	5 years ago
Martin Atkins	f52aec8e3d	website: Fix formatting of v1 compatibility promises ... Seems like we lost a newline in some of the shuffling it took to get this into the live website, and so it's formatting oddly in the rendered website. This restores the intended formatting of this as the start of a bullet list, rather than as a continuation of the previous paragraph.	5 years ago
Judith Malnick	044c439dbc	Gloss of top docs pages (#28891) ... * clarify input variables opening sentence * adjust variables description * claraify providers text and add learn callout * add description to providers page * add desscription and clarify provider configuration * add deprecation note to versions in proivder configs * add hands on callout and clarify next steps in intro * link to language collection from language docs * give more context about configurtion language up front * clarify output top page * reorganize for each intro to present feature before notes * move description before link out and remove passive voice * fix typo * clarify purpose of plan * move explanation before learn link and fully spell boolean * add a syntax heading to separate intro from details * add learn callout to module source docs * clean up intro to provider requirements and add link * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Martin Atkins	07aa07f5b9	website: First Draft of Upgrade Guide	5 years ago
Judith Malnick	d7f6000118	Revert "mclarify specifying provider versions" ... This reverts commit 397494daca.	5 years ago
Judith Malnick	397494daca	mclarify specifying provider versions	5 years ago
Martin Atkins	4e74a7a4f1	initwd: Error message for local paths escaping module packages ... Our module installer has a somewhat-informal idea of a "module package", which is some external thing we can go fetch in order to add one or more modules to the current configuration. Our documentation doesn't talk much about it because most users seem to have found the distinction between external and local modules pretty intuitive without us throwing a lot of funny terminology at them, but there are some situations where the distinction between a module and a module package are material to the end-user. One such situation is when using an absolute rather than relative filesystem path: we treat that as an external package in order to make the resulting working directory theoretically "portable" (although users can do various other things to defeat that), and so Terraform will copy the directory into .terraform/modules in the same way as it would download and extract a remote archive package or clone a git repository. A consequence of this, though, is that any relative paths called from inside a module loaded from an absolute path will fail if they try to traverse upward into the parent directory, because at runtime we're actually running from a copy of the directory that's been taking out of its original context. A similar sort of situation can occur in a truly remote module package if the author accidentally writes a "../" source path that traverses up out of the package root, and so this commit introduces a special error message for both situations that tries to be a bit clearer about there being a package boundary and use that to explain why installation failed. We would ideally have made escaping local references like that illegal in the first place, but sadly we did not and so when we rebuilt the module installer for Terraform v0.12 we ended up keeping the previous behavior of just trying it and letting it succeed if there happened to somehow be a matching directory at the given path, in order to remain compatible with situations that had worked by coincidence rather than intention. For that same reason, I've implemented this as a replacement error message we will return only if local module installation was going to fail anyway, and thus it only modifies the error message for some existing error situations rather than introducing new error situations. This also includes some light updates to the documentation to say a little more about how Terraform treats absolute paths, though aiming not to get too much into the weeds about module packages since it's something that most users can get away with never knowing.	5 years ago
James Bardin	65ee33a90d	Merge pull request #28748 from Bredoxon/patch-1 ... Fix typo in the docs	5 years ago
Bredoxon	06e756eb0c	Fix typo in the docs	5 years ago
James Bardin	760a59b3a7	negative substring	5 years ago
Kyle A. Matheny	3afa08b1bc	Remove duplicate word (#28716)	5 years ago
James Bardin	51a171c7f4	pg requires PostgreSQL 10	5 years ago
Alisdair McDiarmid	3e40a9a4eb	Merge pull request #28507 from stevematney/patch-1 ... Updating sensitive/nonsensitive docs with v0.14 specifics.	5 years ago
Steve Matney	e27a927ba4	Updating sensitive and nonsensitive docs with correct v0.15 info.	5 years ago
Martin Atkins	0aa0e00fdc	website: Backend docs link to new .gitignore anchor ... The Git book seems to be using a different anchor format now, and so this link was previously effectively linking to the page as a whole rather than to the specific section we're trying to refer to.	5 years ago
Martin Atkins	874f1abb2b	cli+website: -ignore-remote-version docs and other cleanup ... We previously had only very short descriptions of what -ignore-remote-version does due to having the documentation for it inline on many different command pages and -help output. Instead, we'll now centralize the documentation about this argument on the remote backend page, and link to it or refer to it from all other locations. This then allows us to spend more words on discussing what Terraform normally does _without_ this option and warning about the consequences of using it. This continues earlier precedent for some local-backend-specific options which we also don't recommend for typical use. While this does make these options a little more "buried" than before, that feels justified given that they are all "exceptional use only" sort of options where users ought to learn about various caveats before using them. While there I also took this opportunity to fix some earlier omissions with the local-backend-specific options and a few other minor consistency tweaks.	5 years ago
Roger Berlind	b6885923d0	website: Add link to Modules in Package Sub-directories (#27980) ... * Add link to Modules in Package Sub-directories Add link to "Modules in Package Sub-directories" section at top of page * Fix broken links * Update aws link, fixes missing anchor linkcheck Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>	5 years ago
Martin Atkins	6f68065326	website: Explicit example of for_each chaining between resources ... This pattern follows as a natural consequence of how for_each is defined, but I've noticed from community forum Q&A that newcomers often don't immediately notice the connection between what for_each expects as input and what a for_each resource produces as a result, so my aim here is to show a short example of that in the hope of helping folks see the link here and get ideas on how to employ the technique in other situations.	5 years ago
Rachel Sharp	c302fa507f	Add link to lifecycle tutorial	5 years ago
John Houston	fabdf0bea1	Add config_paths and drop KUBECONFIG env variable in kubernetes backend (#26997)	5 years ago
Martin Atkins	5f5432e8ea	website: v0.15 upgrade guide for sensitive resource attributes (#28355) ... * website: v0.15 upgrade guide for sensitive resource attributes Our earlier draft of this guide didn't include a section about the stabilization of the "provider_sensitive_attrs" language experiment. This new section aims to address the situation where a module might previously have been returning a sensitive value without having marked it as such, and thus that module will begin returning an error after upgrading to Terraform v0.15. As part of that, I also reviewed the existing documentation about these features and made some edits aiming to make these four different sections work well together if users refer to them all at once, as they are likely to do if they follow the new links from the upgrade guide. I aimed to retain all of the content we had before, but some of it is now in a new location. In particular, I moved the discussion about the v0.14 language experiment into the upgrade guide, because it seems like a topic only really relevant to those upgrading from an earlier version and not something folks need to know about if they are using Terraform for the first time in v0.15 or later. * minor fixups Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
Martin Atkins	140c613ae8	lang/funcs: "one" function ... In the Terraform language we typically use lists of zero or one values in some sense interchangably with single values that might be null, because various Terraform language constructs are designed to work with collections rather than with nullable values. In Terraform v0.12 we made the splat operator [*] have a "special power" of concisely converting from a possibly-null single value into a zero-or-one list as a way to make that common operation more concise. In a sense this "one" function is the opposite operation to that special power: it goes from a zero-or-one collection (list, set, or tuple) to a possibly-null single value. This is a concise alternative to the following clunky conditional expression, with the additional benefit that the following expression is also not viable for set values, and it also properly handles the case where there's unexpectedly more than one value: length(var.foo) != 0 ? var.foo[0] : null Instead, we can write: one(var.foo) As with the splat operator, this is a tricky tradeoff because it could be argued that it's not something that'd be immediately intuitive to someone unfamiliar with Terraform. However, I think that's justified given how often zero-or-one collections arise in typical Terraform configurations. Unlike the splat operator, it should at least be easier to search for its name and find its documentation the first time you see it in a configuration. My expectation that this will become a common pattern is also my justification for giving it a short, concise name. Arguably it could be better named something like "oneornull", but that's a pretty clunky name and I'm not convinced it really adds any clarity for someone who isn't already familiar with it.	5 years ago
Víctor Felipe Godoy Hernández	a9487c7674	Fix yamldecode example from json to yaml (#28220) ... * Fix yamldecode example from json to yaml * inline yaml example	5 years ago
Martin Atkins	f47c4efb1b	website: Dynamic blocks can for_each any collection type ... We previously added a hint to both resource for_each and dynamic blocks about using the "flatten" and "setproduct" situations to construct suitable collections to repeat over. However, we used the same text in both places which ended up stating that dynamic blocks can only accept map or set values, which is a constraint that applies to resource for_each (because we need to assign a unique identifier to each instance) and not to dynamic blocks (which don't have any uniqueness enforced by Terraform Core itself). To remove that contradiction with the text above which talks about what is valid here, I've just generalized this to say "collection", because the primary point of this paragraph is the "one element per desired nested block" part, not specifically what sort of collections are permitted in this location. (Text further up describes the supported types.)	5 years ago
Matthew Frahry	15779013da	backend/azurerm: Bug fixes and updated dependencies #28181	5 years ago
Martin Atkins	6f35c2847b	command: Reorganize docs of the local backend's legacy CLI options ... We have these funny extra options that date back to before Terraform even had remote state, which we've preserved along the way by most recently incorporating them as special-case overrides for the local backend. The documentation we had for these has grown less accurate over time as the details have shifted, and was in many cases missing the requisite caveats that they are only for the local backend and that backend configuration is the modern, preferred way to deal with the use-cases they were intended for. We always have a bit of a tension with this sort of legacy option because we want to keep them documented just enough to be useful to someone who finds an existing script/etc using them and wants to know what they do, but not to take up so much space that they might distract users from finding the modern alternative they should consider instead. As a compromise in that vein here I've created a new section about these options under the local backend documentation, which then gives us the space to go into some detail about the various behaviors and interactions and also to discuss their history and our recommended alternatives. I then simplified all of the other mentions of these in command documentation to just link to or refer to the local backend documentation. My hope then is that folks who need to know what these do can still find the docs, but that information can be kept out of the direct path of new users so they can focus on learning about remote backends instead. This is certainly not the most ideal thing ever, but it seemed like the best compromise between the competing priorities I described above.	5 years ago
Matthew Frahry	13b41d59f5	Website Test Fix	5 years ago
Matthew Frahry	3546650ac6	backend/azurerm: adding the right role name	5 years ago
Matthew Frahry	a978d4ee99	website: adding the new fields to azurerm	5 years ago
Tej-Singh-Rana	2a49d908b8	fix the typo (#28140)	5 years ago
Pam Selle	683422e54f	Merge pull request #28113 from hashicorp/pselle/provider_sensitive_attrs_docs ... Update documentation for provider_sensitive_attrs experiment	5 years ago
James Bardin	c6278bbe37	Merge pull request #28042 from jasons42/update-workspaces-docs ... Indicate etcdv3 support for multiple workspaces in docs	5 years ago
Martin Atkins	89b2405080	lang/funcs: "sensitive" and "nonsensitive" functions ... These aim to allow hinting to Terraform about situations where it's not able to automatically infer value sensitivity. "nonsensitive" is for situations where Terraform's behavior is too conservative, such as when a new value is derived from a sensitive value in such a way that all of the sensitive content is removed. "sensitive", on the other hand, is for situations where Terraform can't otherwise infer that a value is sensitive. These situations should be pretty rare in a module that's making effective use of sensitive input variables and output values, but the documentation shows one example of an uncommon situation where a more direct hint via this function would be needed. Both of these functions are aimed at only occasional use in unusual situations. They are here for reasons of pragmatism, not because we expect them to be used routinely or recommend their use.	5 years ago
Pam Selle	81e8167a4c	Update documentation for provider_sensitive_attrs experiment ... Update documentation to reference that this experiment is now default in 0.15+	5 years ago
Jason Smith	024035114a	Fix broken link error ... Link to https://consul.io/ is not actually broken but returns a 307 redirect to https://www.consul.io/ which the broken link test counts as a failure.	5 years ago
Jason Smith	8663b2100a	Indicate etcdv3 support for multiple workspaces	5 years ago
Antoine Cotten	3442873cdb	docs: Update link to HCL native syntax spec	5 years ago
Aaron Lane	f172585eaa	Fix Kitchen-Terraform language in test experiment ... This isn't incredibly important, but Kitchen-Terraform is written in and requires tests to be written in Ruby.	5 years ago
Kristin Laemmert	106bcd3bf0	update to match new default branch name (#27909)	5 years ago
Alisdair McDiarmid	79f855b83b	Merge pull request #27840 from OJFord/docs-27554 ... Document `inline` & `on_failure` behaviour	5 years ago
Martin Atkins	8d37a70987	website: Initial docs for the module integration testing experiment ... Since this is still at an early phase and likely to change significantly in future iterations, rather than attempting to guess on a suitable final location for documenting the testing feature I've instead taken the unusual approach of adding a new page that is explicitly about the experiment. My expectation is that once we conclude the experiment we'll replace this new page with a stub that just explains that there was once an experiment and then links to whatever final feature unfolded from the research. The URL for this page is hard-coded into the warning message in the "terraform test" command, so as we continue to evolve this feature in future releases we'll need to update the callout note on the page about which Terraform CLI version it's currently talking about, so users of older versions can clearly see when they'd need to upgrade in order to participate in a later incarnation of the experiment.	5 years ago
Oliver Ford	2f7c368d91	Document `inline` & `on_failure` behaviour ... cf. #27554	5 years ago
Pam Selle	8d2fbd4cd8	Remove deprecation on undeclared variable, docs, and summary adjustment (#27795) ... * Remove deprecation on undeclared variable Remove deprecation and add docs specific to the behavior around undeclared variable values * Limit full warnings to 2 instances, then summary This way, the third warning is a summary, rather than the fourth warning being the summary	5 years ago
James Bardin	d54a9b176b	Update website/docs/language/providers/configuration.html.md ... Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com>	5 years ago
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
Nick Fagerlund	4e4f6b3f42	website: Restore note about standard vs. enhanced backends	5 years ago
Nick Fagerlund	d1e8537b33	website: CLI: Update links to moved docs pages	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