terraform

Commit Graph

Author	SHA1	Message	Date
Alisdair McDiarmid	c5c1f31db3	backend: Validate remote backend Terraform version When using the enhanced remote backend, a subset of all Terraform operations are supported. Of these, only plan and apply can be executed on the remote infrastructure (e.g. Terraform Cloud). Other operations run locally and use the remote backend for state storage. This causes problems when the local version of Terraform does not match the configured version from the remote workspace. If the two versions are incompatible, an `import` or `state mv` operation can cause the remote workspace to be unusable until a manual fix is applied. To prevent this from happening accidentally, this commit introduces a check that the local Terraform version and the configured remote workspace Terraform version are compatible. This check is skipped for commands which do not write state, and can also be disabled by the use of a new command-line flag, `-ignore-remote-version`. Terraform version compatibility is defined as: - For all releases before 0.14.0, local must exactly equal remote, as two different versions cannot share state; - 0.14.0 to 1.0.x are compatible, as we will not change the state version number until at least Terraform 1.1.0; - Versions after 1.1.0 must have the same major and minor versions, as we will not change the state version number in a patch release. If the two versions are incompatible, a diagnostic is displayed, advising that the error can be suppressed with `-ignore-remote-version`. When this flag is used, the diagnostic is still displayed, but as a warning instead of an error. Commands which will not write state can assert this fact by calling the helper `meta.ignoreRemoteBackendVersionConflict`, which will disable the checks. Those which can write state should instead call the helper `meta.remoteBackendVersionCheck`, which will return diagnostics for display. In addition to these explicit paths for managing the version check, we have an implicit check in the remote backend's state manager initialization method. Both of the above helpers will disable this check. This fallback is in place to ensure that future code paths which access state cannot accidentally skip the remote version check.	5 years ago
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	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
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
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
Daniel Dreier	df39e0a806	Merge pull request #23989 from tatsuo48/fix_sample_code fix sample code	6 years ago
Alisdair McDiarmid	52d64127f7	website: Add docs for state replace-provider	6 years ago
yokoyama tatsuo	a280e2ffea	fix sample code	6 years ago
Martin Atkins	2a95d98383	docs: terraform state show is not machine-readable In earlier versions of Terraform the result of terraform state show was in the pre-0.12 "flatmap" structure that was unable to reflect nested data structures. That was fixed in Terraform 0.12, but as a consequence this statement about the output being machine-parseable (which was debateable even in older versions) is incorrect. Fortunately, we now have "terraform show -json" to get output that is intentionally machine-parseable, so we'll recommend to use that instead here. The JSON output of that command is a superset of what's produced by "terraform state show", so should be usable to meet any use-case that might previously have been met by parsing the "terraform state show" output.	6 years ago
Brian Flad	3a1a39bed3	docs/commands: Switch using count/for_each to configured with count/for_each Reference: https://github.com/hashicorp/terraform/pull/22318#discussion_r310587243	7 years ago
Brian Flad	48624255ce	docs/commands: Show count and for_each resource address examples for commands Verified on Mac OS 10.14.6 and Windows 10.	7 years ago
Justin Downing	1e32ae243c	grammatical updates to comments and docs (#20195 )	7 years ago
Martin Atkins	04f3766fd9	website: Indicate v0.12-only content We have released the v0.12-oriented content to the website early in order to support the beta process, but in some places we neglected to explicitly mark features or content as being v0.12-only. Here we add explicit markers to the main cases we've seen where readers have reported confusion, along with some other tweaks in similar vein.	7 years ago
Nick Fagerlund	0fddabf972	website: Reorganize nav sidebars to improve jumps between sections	7 years ago
Dave Wongillies	9190227bc0	Fix description for state mv and push sub-commands	8 years ago
Uriel Corfa	07a20365de	cli: "terraform state list" -id argument A new -id option to "terraform state list" which constraints the output of the command to resources whose id is equal to the flag value.	8 years ago
James Bardin	55d18dcef2	update state rm amd mv docs Update the documentation to match the current behavior, and make the usage output and website docs match.	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

18 Commits (652b48bb49625e437b797e1a991aa4fa31126dfd)