You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the provider registry is hard coded as registry.terraform.io when looking up providers. For anyone using alternative registries such as registry.opentofu.org or self hosting their own registry, this causes terraformer to fail with an error similar to:
2024/01/29 01:39:14 aws importing default region
2024/01/29 01:39:14 open /home/nullreff/.terraform.d/plugins/linux_amd64: no such file or directory
which is rather hard to track down what's going wrong. Possible fixes I can thing of might be:
Support a CLI flag or configuration option to pick which registry to use
Search all the registries in the plugins directory for the provider we're looking for
If the default registry isn't found, prompt the user to pick from any others found
As for workarounds, the best way I've found is to symlink the expected provider directory to the one you're using.
For example using registry.opentofu.org:
Right now the provider registry is hard coded as registry.terraform.io when looking up providers. For anyone using alternative registries such as
registry.opentofu.org
or self hosting their own registry, this causes terraformer to fail with an error similar to:which is rather hard to track down what's going wrong. Possible fixes I can thing of might be:
plugins
directory for the provider we're looking forAs for workarounds, the best way I've found is to symlink the expected provider directory to the one you're using.
For example using
registry.opentofu.org
:However I wouldn't recommend this if you're using a mix of registries as they'll now be installed into the same directory.
The text was updated successfully, but these errors were encountered: