39 Commits (f-langserver)

Author	SHA1	Message	Date
Nick Fagerlund	a797152648	website: Remove extra copy of "Running Terraform in Automation", update links ... This document now lives at: - https://learn.hashicorp.com/terraform/development/running-terraform-in-automation ...and terraform.io has been redirecting to there for quite a while. This commit removes the extra copy so that the text of the two versions doesn't drift, and updates existing links to point to the new location.	6 years ago
Martin Atkins	7cf782c1bf	states/statefile: Better error messages for some unsupported v3 cases ... There are a few situations that we've seen arise quite commonly for folks upgrading from Terraform 0.11 to 0.12. These particular problems are not things that Terraform 0.12 can fix automatically during upgrading, but we can at least give some better feedback to users that they ought to be addressed _before_ upgrading. The provider address problem is already detected and flagged by the "terraform 0.11checklist" command that folks should run as part of their upgrade process, but the module address problem is not something we noticed was lacking validation in 0.11 and so the checklist tool doesn't cover it. Due to the lack of coverage in the checklist tool, this commit also includes an additional section in the upgrade guide that mentions the problem and gives instructions on how to address it.	7 years ago
Nick Fagerlund	3aa909ac6e	website: Update URLs and name references for Terraform Cloud rebrand ... The Terraform Enterprise brand has now been split into two parts: - Terraform Cloud is the application that helps teams use Terraform together, with remote state storage, a shared run environment, etc. - Terraform Enterprise is the on-premise distribution that lets enterprises run a private instance of the Terraform Cloud application. The former TFE docs have been split accordingly.	7 years ago
Dan LaMotte	27ecace1a1	Properly end code block in upgrade docs ... The unterminated code block effectively breaks rendering in the latter half of this section https://www.terraform.io/upgrade-guides/0-12.html#equality-operations-must-be-valid-on-value-and-type	7 years ago
Pam Selle	0a893f8c53	Update to equality vs comparison	7 years ago
Pam Selle	f184d2c62a	Docs to assist with #21978	7 years ago
Yuri Astrakhan	0bd29ce194	clarify config block in terraform_remote_state ... This seems to be a common mistake - saw it in StackOverflow and in several issues.	7 years ago
petems	239c84ef4b	Minor spelling fixes ... `docker run -v $(pwd):/scripts --workdir=/scripts nickg/misspell:latest misspell -w -source=text website/`	7 years ago
Joe Tavin	2c176fdf4b	website/0.12 upgrade: Fix typo (#21426)	7 years ago
Chris Marchesi	340aa7c598	website: add Sentinel 0.12 upgrade guide details ... This adds details for using Sentinel in Terraform 0.12. It largely links to the corresponding guide in the Terraform Enterprise documentation.	7 years ago
Martin Atkins	fe8c380fe1	website: Remove the Sentinel section from 0.12 upgrade guide ... A longer-form guide will follow in the Sentinel section of the Terraform Enterprise documentation, once it's ready. For now, this section isn't saying anything useful since it was always just a stub for a guide we planned to write later.	7 years ago
Martin Atkins	32d19b9574	website: 0.12 upgrade guide about variable type constraints ... The upgrade tool is assuming that a type of "list" means list(string) and a type of "map" means map(string), because that was what we documented those as meaning. In practice, Terraform 0.11 was lacking some validation which allowed more complex nested structures in some cases even though they were pretty inconvenient to use due to other language limitations. The upgrade tool doesn't have enough context to make a reliable decision on this, so instead we'll rely on the upgrade guide for this. We don't need a TF-UPGRADE-TODO comment in this case because we reserve those for things where a subsequent operation might cause the configuration to be misinterpred, rather than just causing an error. Instead, we'll show an example of the comment in the upgrade guide so the reader can easily match it, and give some advice in the guide on how to address it.	7 years ago
Martin Atkins	c6e32f148d	website: v0.12 upgrade guide revisions preparing for final release ... Our original upgrade guide was drafted while some things were still in flux and not all of our upgrade tooling was in place yet. This redraft now attempts to be more specific and direct, showing exact commands to run and (where relevant) exact error messages that Terraform might return. I also took this opportunity for some general copy-editing, though we'll probably want to do one more pass of that alone (without changing any content at the same time) before final release. This new content presumes the existence of a Terraform v0.11.14 release, which isn't published yet at the time of writing but should be published before v0.12.0 final, once we've done final verification and review of the upgrade path including it.	7 years ago
Kristin Laemmert	b66d03bba7	Mildwonkey/upgrade doc remote backend (#21201) ... * website/upgrade-guides: init -reconfigure is required with remote backend * build: add a real and useful version of `.tfdev`	7 years ago
Martin Atkins	2238fbda1b	website: v0.12 upgrade guide about list variables and brackets	7 years ago
Martin Atkins	c94f8f9067	website: Document division behavior change in v0.12 upgrade guide ... The division operator now always performs floating point division, whereas before it would choose between float and int division based on the types of its arguments. We have a specific error message for when a fractional number is used as an index in HCL, but this additional upgrade guidance provides a specific solution to the problem: the floor function. Sadly we don't have enough context in the current design of the upgrade tool to make this fix automatic. With some refactoring it may be possible to apply the fix automatically within list brackets, but since that is a relatively complex change we'll first try this manual solution prompted by an error message, because in practice so far we've seen this reported only in the context of list indexing and our error check will catch that and make the user aware of the need for a fix there.	7 years ago
Nick Fagerlund	cb4f3004da	website: Fix several spelling errors	7 years ago
Nick Fagerlund	34e90ff3c1	website: Fix broken links to modules/usage and modules/create ... As part of this, I'm copying the entire text of the 0.12 docs/configuration/modules.html page into docs/configuration-0-11/modules.html — some of the 0.11 pages needed to be able to link to the moved content, I didn't want to jump versions jarringly, and a close reading didn't reveal anything in there that's inaccurate for 0.11.	7 years ago
Kristin Laemmert	21f6e3dffd	Mildwonkey/012 docs updated (#20542) ... * docs: update plan command documentation. Fixes #19235 * docs: added a missing reserved variable name. Fixes #19159. * website: add note that resource names cannot start with a number * website: add some notes to the 0.12 upgrade guide	7 years ago
Martin Atkins	08f0f60908	website: Temporary link to the beta1 announcement from v0.12 guide ... The announcement post contains the information about the temporary situation where not all of the providers are compatible yet. Linking there rather than duplicating the information in the upgrade guide means we'll be able to update in one place as the situation changes.	7 years ago
Martin Atkins	da4862e3f7	website: Revamped upgrade guide for v0.12.0-beta1 ... The upgrade guide had its last major upgrade while we were preparing for the alpha releases. Now that the upgrade tool is more complete we can describe the required changes in terms of that tool, and also add additional information about provider upgrades. We will revise this at least one more time before v0.12.0 final, but this is an interim copy of the upgrade guide intended to help those who are testing the beta releases.	7 years ago
Radek Simko	5ffb106783	docs/upgrade-guide: Document changes in remote state referencing	7 years ago
Nick Fagerlund	0fddabf972	website: Reorganize nav sidebars to improve jumps between sections	7 years ago
Alex Gottschalk	029f54792f	remove approximate release date ... "Later this summer" is long-gone.	7 years ago
Martin Atkins	9441e78fb9	website: v0.12 preview upgrade guide tweaks ... Based on some feedback on the initial draft, make some minor updates to how information is presented in the preview upgrade guide for v0.12. This also includes some minor copy-editing work to try to make the "voice" more consistent between different sections of the guide.	8 years ago
kfishner	6deec5d7bf	add 0.12 guide	8 years ago
Thomas Kula	e2373c8073	website: Using demo.consul.io requires scheme = "https" ... Following the examples as they were previously would cause errors accessing demo.consul.io. Now we consistently set the scheme to https for all examples that use demo.consul.io. This also includes some other updates to the URLs, since the Consul demo has been rebuilt with a different based configuration, and some general formatting and copyediting changes in the Consul example.	8 years ago
James Bardin	1940e213a0	reword inheritance upgrade guide	9 years ago
Martin Atkins	57db3cfe51	website: 0.11 upgrade guidance on resources with count = 0 ... This is a genre of invalid output expression that we've seen quite commonly while testing with 0.11.0-rc1, so we'll call it out specifically in the upgrade guide and suggest how to fix it.	9 years ago
Martin Atkins	f3f0b5356e	website: specify HCL syntax highlighting in the 0.11 upgrade guide	9 years ago
Martin Atkins	071e746edf	website: use correct style for providers map in upgrade guide ... We don't generally use comma separators for map elements in HCL, because the newline implies it.	9 years ago
Martin Atkins	1622a63da5	website: use correct syntax for providers map in upgrade guide ... This was using JSON-style syntax rather than HCL-style.	9 years ago
Martin Atkins	11790442a1	website: Describe provider config hoisting in 0.11 upgrade guide ... We are recommending that as of 0.11 all provider configurations be placed in the root module and, where necessary, be explicitly passed down via a providers map to customize which configurations are seen by each child module. This new section attempts to guide users through such refactoring in the common case where a child module defines its own provider configuration based on a value passed in an input variable, and then uses that as some context to link to the more detailed docs to help those who have more complex configurations.	9 years ago
Andy Brody	4b1c7a1d9b	website: Fix broken link in 0.10 upgrade guide	9 years ago
Martin Atkins	56a9b1309a	website: initial draft of 0.11 upgrade guide ... This will be revised further as we near the final release. This contains notes on changes that have already been merged.	9 years ago
Martin Atkins	0543574383	website: update upgrade-guide for plugin filename convention ... This changed close to the release of beta1 to use underscores as the separator and to use a lower-case "v" to avoid any issues on case-insensitive filesystems.	9 years ago
Robert Liebowitz	8d98fdecac	Autoload only .auto.tfvars files	9 years ago
Robert Liebowitz	006744bfe0	Use all tfvars files in working directory ... As a side effect, several commands that previously did not have a failure state can now fail during meta-parameter processing.	9 years ago
Martin Atkins	7ed70bb00e	website: new filesystem layout for core/provider split ... This repo now contains only the core docs, with other content moving elsewhere.	9 years ago