Terraform init无法验证校验和

Terraform init无法验证校验和,terraform,Terraform,在公司代理之后在windows 10上使用Terraform v0.12.5 当我跑的时候 地形初始 然后我得到了 Initializing the backend... Initializing provider plugins... - Checking for available provider plugins... Error verifying checksum for provider "helm" The checksum for provider distribution

在公司代理之后在windows 10上使用Terraform v0.12.5

当我跑的时候 地形初始 然后我得到了

Initializing the backend...

Initializing provider plugins...
- Checking for available provider plugins...

Error verifying checksum for provider "helm"
The checksum for provider distribution from the Terraform Registry
did not match the source. This may mean that the distributed files
were changed after this version was released to the Registry.

...

Error: unable to verify checksum
对于我的团队成员来说,它工作得很好(相同的terraform版本,但在linux环境中,使用VPN。他们没有代理地狱)

我将代理设置为env variabes(HTTP\u代理和HTTPS\u代理)

如果我不设置它们,我就有

Error: error validating provider credentials: error calling sts:GetCallerIdentity: RequestError: send request failed
caused by: Post https://sts.amazonaws.com/: dial tcp --.--.--.--:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
相反


我认为这是一个网络问题,但上面的错误一点也不详细。

terraform init-重新配置应该可以工作。它将重新下载所有连接器并重置错误的后端名称。

terraform init-重新配置应该可以工作。它将重新下载所有连接器并重置错误的后端名称。

您的代理是否会改变一切?如果从注册表中卷曲Helm提供程序二进制文件(
curl-o Helm.zip)https://releases.hashicorp.com/terraform-provider-helm_/terraform-provider-helm___?Does 如果您从注册表中卷曲Helm provider二进制文件,那么您的代理是否会改变一切(
curl-o helm.ziphttps://releases.hashicorp.com/terraform-provider-helm_/terraform-provider-helm___?