terraform/command/e2etest
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.
2017-11-01 06:54:39 -07:00
..
test-fixtures command/e2etest: test installation of plugins from cache 2017-09-29 14:03:09 -07:00
.gitignore command/e2etest: end-to-end testing harness 2017-07-17 14:25:33 -07:00
automation_test.go command: "terraform apply" uses interactive confirmation by default 2017-11-01 06:54:39 -07:00
doc.go command/e2etest: end-to-end testing harness 2017-07-17 14:25:33 -07:00
init_test.go e2e test for `init -from-module` 2017-10-30 11:32:40 -04:00
main_test.go Use t.Helper() in our test helpers 2017-08-28 09:59:30 -07:00
make-archive.sh command/e2etest: end-to-end testing harness 2017-07-17 14:25:33 -07:00
primary_test.go command/e2etest: test the "running in automation" workflow 2017-09-28 14:35:51 -07:00
version_test.go command: Include provider versions in "terraform version" 2017-10-25 17:36:24 -07:00