terraform/internal/initwd
Alisdair McDiarmid 62d826e066 command/init: Use full config for provider reqs
Relying on the early config for provider requirements was necessary in
Terraform 0.12, to allow the 0.12upgrade command to run after init
installs providers.

However in 0.13, the same restrictions do not apply, and the detection
of provider requirements has changed. As a result, the early config
loader gives incorrect provider requirements in some circumstances,
such as those in the new test in this commit.

Therefore we are changing the init command to use the requirements found
by the full configuration loader. This also means that we can remove the
internal initwd CheckCoreVersionRequirements function.
2020-05-25 16:50:12 -04:00
..
testdata Standardise directory name for test data 2019-06-30 10:16:15 +02:00
doc.go command: "terraform init" can partially initialize for 0.12upgrade 2019-01-14 11:33:21 -08:00
from_module.go internal/copydir: Factor out our recursive directory copy for reuse 2020-03-25 11:29:48 -07:00
from_module_test.go backend/remote-state: etcdv3, oss, and manta acc tests should fail 2019-09-27 08:45:12 -04:00
getter.go internal/copydir: Factor out our recursive directory copy for reuse 2020-03-25 11:29:48 -07:00
load_config.go command: "terraform init" can partially initialize for 0.12upgrade 2019-01-14 11:33:21 -08:00
module_install.go registry: configurable retry client 2020-02-14 13:29:00 -06:00
module_install_hooks.go Move module install functionality over to internal/initwd 2019-01-14 11:33:21 -08:00
module_install_test.go internal/copydir: Factor out our recursive directory copy for reuse 2020-03-25 11:29:48 -07:00
testing.go command: "terraform init" can partially initialize for 0.12upgrade 2019-01-14 11:33:21 -08:00