terraform/internal/providercache
Martin Atkins 4b3e237668 command/init: Hint about providers in other namespaces
If a user forgets to specify the source address for a provider, Terraform
will assume they meant a provider in the registry.terraform.io/hashicorp/
namespace. If that ultimately doesn't exist, we'll now try to see if
there's some other provider source address recorded in the registry's
legacy provider lookup table, and suggest it if so.

The error message here is a terse one addressed primarily to folks who are
already somewhat familiar with provider source addresses and how to
specify them. Terraform v0.13 had a more elaborate version of this error
message which directed the user to try the v0.13 automatic upgrade tool,
but we no longer have that available in v0.14 and later so the user must
make the fix themselves.
2020-12-10 10:11:27 -08:00
..
testdata providercache: More exhaustive testing of the main installer 2020-10-28 07:46:45 -07:00
cached_provider.go command/init: Read, respect, and update provider dependency locks 2020-10-09 09:26:23 -07:00
cached_provider_test.go
dir.go command/init: Read, respect, and update provider dependency locks 2020-10-09 09:26:23 -07:00
dir_modify.go command/init: Read, respect, and update provider dependency locks 2020-10-09 09:26:23 -07:00
dir_modify_test.go command/init: Read, respect, and update provider dependency locks 2020-10-09 09:26:23 -07:00
dir_test.go
doc.go
installer.go command/init: Hint about providers in other namespaces 2020-12-10 10:11:27 -08:00
installer_events.go command/init: Mention using the lock file for provider selection 2020-10-09 09:26:23 -07:00
installer_events_test.go providercache: More exhaustive testing of the main installer 2020-10-28 07:46:45 -07:00
installer_test.go normalize temp dir paths in tests 2020-11-20 16:35:31 -05:00
package_install.go internal/providercache: staticcheck 2020-12-02 13:59:20 -05:00