9d623290f4
If you run the e2etests locally and use a configured plugin_cache_dir, the test will leave a bad directory behind in your cache dir that causes later `init`s to fail. To circumvent this, pass an explicity-empty CLI config file. This is a nicety for local developers and not necessarily required, but it happens to me often enough that I'd like to fix it. It's probably not a *bad* idea to pass an explicit cli config to all e2etests, honestly, but this is the only one that causes active problems so I limited this PR to that one test. Here's the error which occurs on subsequent `init` if this test is run on a machine that uses a plugin cache dir: 2020/10/13 10:41:05 [TRACE] providercache.fillMetaCache: error while scanning directory /Users/mildwonkey/.terraform.d/plugin-cache: failed to read metadata about /Users/mildwonkey/.terraform.d/plugin-cache/example.com/awesomecorp/happycloud/1.2.0/darwin_amd64: stat /Users/mildwonkey/.terraform.d/plugin-cache/example.com/awesomecorp/happycloud/1.2.0/darwin_amd64: no such file or directory |
||
|---|---|---|
| .. | ||
| testdata | ||
| .gitignore | ||
| automation_test.go | ||
| doc.go | ||
| init_test.go | ||
| main_test.go | ||
| make-archive.sh | ||
| primary_test.go | ||
| provider_dev_test.go | ||
| providers_mirror_test.go | ||
| remote_state_test.go | ||
| unmanaged_test.go | ||
| version_test.go | ||