terraform/command/e2etest/testdata
Paddy 5127f1ef8b
command: Unmanaged providers
This adds supports for "unmanaged" providers, or providers with process
lifecycles not controlled by Terraform. These providers are assumed to
be started before Terraform is launched, and are assumed to shut
themselves down after Terraform has finished running.

To do this, we must update the go-plugin dependency to v1.3.0, which
added support for the "test mode" plugin serving that powers all this.

As a side-effect of not needing to manage the process lifecycle anymore,
Terraform also no longer needs to worry about the provider's binary, as
it won't be used for anything anymore. Because of this, we can disable
the init behavior that concerns itself with downloading that provider's
binary, checking its version, and otherwise managing the binary.

This is all managed on a per-provider basis, so managed providers that
Terraform downloads, starts, and stops can be used in the same commands
as unmanaged providers. The TF_REATTACH_PROVIDERS environment variable
is added, and is a JSON encoding of the provider's address to the
information we need to connect to it.

This change enables two benefits: first, delve and other debuggers can
now be attached to provider server processes, and Terraform can connect.
This allows for attaching debuggers to provider processes, which before
was difficult to impossible. Second, it allows the SDK test framework to
host the provider in the same process as the test driver, while running
a production Terraform binary against the provider. This allows for Go's
built-in race detector and test coverage tooling to work as expected in
provider tests.

Unmanaged providers are expected to work in the exact same way as
managed providers, with one caveat: Terraform kills provider processes
and restarts them once per graph walk, meaning multiple times during
most Terraform CLI commands. As unmanaged providers can't be killed by
Terraform, and have no visibility into graph walks, unmanaged providers
are likely to have differences in how their global mutable state behaves
when compared to managed providers. Namely, unmanaged providers are
likely to retain global state when managed providers would have reset
it. Developers relying on global state should be aware of this.
2020-05-26 17:48:57 -07:00
..
custom-provider-install-method main: Properly handle provider installation method exclusions 2020-04-23 10:52:01 -07:00
empty Standardise directory name for test data 2019-06-30 10:16:15 +02:00
full-workflow-null Standardise directory name for test data 2019-06-30 10:16:15 +02:00
local-only-provider main: skip direct provider installation for providers available locally 2020-04-17 13:55:11 -07:00
plugin-cache internal/providercache: Fix incorrect logic in Installer.SetGlobalCacheDir 2020-04-06 09:24:23 -07:00
provider-not-found command/init: add e2e tests for provider not found messages 2020-05-20 11:04:11 -04:00
template-provider Standardise directory name for test data 2019-06-30 10:16:15 +02:00
terraform-provider Standardise directory name for test data 2019-06-30 10:16:15 +02:00
test-provider command: Unmanaged providers 2020-05-26 17:48:57 -07:00
vendored-provider command/init: Move "vendored provider" test to e2etests 2020-04-06 09:24:23 -07:00