8 Commits (6440c839474f052d8997bb5cec19c2743e5108e6)

Author	SHA1	Message	Date
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
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
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	011e84f32f	website: Update example command list for 0.12	7 years ago
Martin Atkins	adbb9d0cf9	website: checkpoint settings refer to CLI config file docs ... Previously we described inline here where to put the .terraformrc file, but now we have a separate page all about this file that gives us more room to describe in more detail where the file is placed and what else it can do.	9 years ago
Martin Atkins	2c782e60fa	website: documentation for the shell tab-completion support	9 years ago
Martin Atkins	f6dace3476	website: document the Checkpoint service and how to disable it ... This is documented for all other Hashicorp products using this service but was missed for Terraform. This serves as a disclosure of the fact that Terraform reaches out to a Hashicorp service, an explanation of the purpose of that request, and instructions on how to disable it in environments where it is inappropriate or cannot be supported due to a firewall or other connectivity restrictions.	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