19 Commits (7ee433955536db3fdff2dba9548cd2e88ae8a43c)

Author	SHA1	Message	Date
Paul Hinze	6cdc464341	Initial draft of Core Workflow Guide	8 years ago
Clint Shryock	26b68d98f9	update some content to reference the extending terraform section	8 years ago
Michał Kiełtyka	8add05f6ee	website: Remove errant "the" in the running-in-automation guide	8 years ago
Johannes Liebermann	6a493f37d3	Update running-terraform-in-automation.html.md ... Fix word ordering	8 years ago
AV Jafrey	725281f4aa	website: Fix typo in the provider development program guide	8 years ago
Yaron Tal	a40eac1cca	Small typo fix in provider documentation	8 years ago
Hunter Morgan	703673fb9e	website: fix typo in the guide to writing Terraform providers	8 years ago
Martin Atkins	400038eda4	command: "terraform apply" uses interactive confirmation by default ... In the 0.10 release we added an opt-in mode where Terraform would prompt interactively for confirmation during apply. We made this opt-in to give those who wrap Terraform in automation some time to update their scripts to explicitly opt out of this behavior where appropriate. Here we switch the default so that a "terraform apply" with no arguments will -- if it computes a non-empty diff -- display the diff and wait for the user to type "yes" in similar vein to the "terraform destroy" command. This makes the commonly-used "terraform apply" a safe workflow for interactive use, so "terraform plan" is now mainly for use in automation where a separate planning step is used. The apply command remains non-interactive when given an explicit plan file. The previous behavior -- though not recommended -- can be obtained by explicitly setting the -auto-approve option on the apply command line, and indeed that is how all of the tests are updated here so that they can continue to run non-interactively.	9 years ago
Martin Atkins	0fe43c8977	cli: allow disabling "next steps" message in terraform plan ... In #15884 we adjusted the plan output to give an explicit command to run to apply a plan, whereas before this command was just alluded to in the prose. Since releasing that, we've got good feedback that it's confusing to include such instructions when Terraform is running in a workflow automation tool, because such tools usually abstract away exactly what commands are run and require users to take different actions to proceed through the workflow. To accommodate such environments while retaining helpful messages for normal CLI usage, here we introduce a new environment variable TF_IN_AUTOMATION which, when set to a non-empty value, is a hint to Terraform that it isn't being run in an interactive command shell and it should thus tone down the "next steps" messaging. The documentation for this setting is included as part of the "...in automation" guide since it's not generally useful in other cases. We also intentionally disclaim comprehensive support for this since we want to avoid creating an extreme number of "if running in automation..." codepaths that would increase the testing matrix and hurt maintainability. The focus is specifically on the output of the three commands we give in the automation guide, which at present means the following two situations: * "terraform init" does not include the final paragraphs that suggest running "terraform plan" and tell you in what situations you might need to re-run "terraform init". * "terraform plan" does not include the final paragraphs that either warn about not specifying "-out=..." or instruct to run "terraform apply" with the generated plan file.	9 years ago
Mitchell Hashimoto	b8f7436948	website: address changes from @catsby	9 years ago
Mitchell Hashimoto	d4286dcd8c	website: new provider dev program content ... This brings back the provider dev program content with a copy change. Reviewed by Burzin already, requesting review from Clint.	9 years ago
clint shryock	f291994a3f	Guides: remove the provider development program for now	9 years ago
Alex Tasioulis	5f3e76203b	Fix titles on partner contact table on provider development program guide ... "Website" and "Email" were the wrong way around.	9 years ago
James Bardin	a56a97a5f5	mention 'terraform.d/plugins` for automation	9 years ago
Kelly Brownsberger	40bb7612c1	small typo correction ... 'used used' => 'used'	9 years ago
Nick Fagerlund	8c7bfde292	Docs: Fix broken links and a broken example ... These links were casualties of the core/provider split. There was also an example that suggested cloning a subdirectory of a git repo.	9 years ago
Clint	9b9bfb9fec	Add provider dev program guide (#15677) ... * Add provider dev program guide Requires assets from https://github.com/hashicorp/terraform-website/pull/12 * editing from feedback * add spaces after ##	9 years ago
Martin Atkins	63d4c0efe1	website: guide to running Terraform in automation ... This guide covers assorted best practices and caveats for running Terraform within orchestration tools and other automation. It provides general examples and guidance, with the intent that this advice can be adapted by the reader to a concrete implementation within a selected orchestration tool. This guide is based both on our in-house experience with Terraform Enterprise and on in-house solutions we are aware of in certain organizations.	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