Closed phazeight closed 2 months ago
welp found this thread https://discuss.hashicorp.com/t/failed-to-instantiate-provider-to-obtain-schema-looking-for-tips-to-diagnose-the-problem/14959/6 which was enough to convince me it was a weird macos sockets tcp/udp issue with terraform, and restarting my workstation fixed it. really random though, hopefully it doesn't show back up frequently
Describe the Bug
One of my modules is using the provider registry.terraform.io/cloudposse/utils, and when I ran a terraform init and plan today, started seeing this message after successful init.
I cleared the local terraform cache and ran again, but didn't do away with it
Expected Behavior
I expected as something I use nearly daily for my terraform init and plan to resolve using this module
Steps to Reproduce
not sure, seems to be a provider level issue at the moment
Screenshots
Environment
No response
Additional Context
UPDATE Tried another of my repos that uses the same module to eliminate if it was a local issue and got the same message, further supporting that there is some kind of provider level issue happening