I have set the proxy in command as following
set HTTP_PROXY=http://user:passowrd#host.com:8080
set HTTPS_PROXY=https://user:passowrd#host.com:8080
set HTTP_USER=myuser
set HTTP_PASSWORD=mypwd
and future more I have set environment variable as HTTP_PROXY, HTTPS_PROXY, HTTP_USER, HTTP_PASSWORD
Somehow still getting following error
>terraform init
Initializing the backend...
Initializing provider plugins...
- Checking for available provider plugins...
Registry service unreachable.
This may indicate a network issue, or an issue with the requested Terraform Registry.
Error: registry service is unreachable, check https://status.hashicorp.com/ for status updates
please note that https://status.hashicorp.com/ having access behind the proxy.
but I am not sure terraform init actually which URL/service API is getting access
Working for me with proxy:
C:\Users\xxxx\Desktop\VMWare_Scripts\Terraform>set HTTP_PROXY=http://xxxx:8080
C:\Users\xxxx\Desktop\VMWare_Scripts\Terraform>terraform init
Initializing the backend...
Initializing provider plugins...
Finding latest version of hashicorp/vsphere...
Installing hashicorp/vsphere v1.24.1...
Installed hashicorp/vsphere v1.24.1 (signed by HashiCorp)
The following providers do not have any version constraints in configuration,
so the latest version was installed.
To prevent automatic upgrades to new major versions that may contain breaking
changes, we recommend adding version constraints in a required_providers block
in your configuration, with the constraint strings suggested below.
hashicorp/vsphere: version = "~> 1.24.1"
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Related
W0111 13:21:23.866650 172 azure.go:92] WARNING: the azure auth plugin is deprecated in v1.22+, unavailable in v1.26+; use https://github.com/Azure/kubelogin instead.
To learn more, consult https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins
This is the error I get in cmd, powershell, git-bash, azure shell & vscode terminal. Also I get the same issue if I go to the azure portal and use the web shell.
Yes if I use the terminal in Mirantis lens kubectl works as expected the only difference being is that I've added a http proxy in the Proxy settings for Lens.
I belive the issue is caused by the terminal not using the http proxy.
I've added a system environment variable through advanced system settings, which doesn't appear to be used in my terminal session.
How can I use the http proxy during sessions to use kubectl to access AKS and how can I check if the terminal is using the http proxy?
Installed kubelogin as above
Checked that the proxy was running using Get-Proxess px*
Checked that the environment variable was set with the correct value by doing ls $env: and listing all envvars
You are correct, the problem is with the client.
It seems you are using a client version > 1.26, which as the error suggests its removed.
The easiest thing you can do is to use an older version of the kubectl client.
I'm running a terraform plan through AWS Codebuild. terraform init works consistently but terraform plan intermittently throws this error:
Error: rpc error: code = Canceled desc = context canceled
terraform version: 0.12.31
aws provider version: ~> 3.55.0
The intention here was to change Python lambda runtimes from 3.6 to 3.9. In this regard, I upgraded terraform from 0.12.21 to 0.12.31 and aws provider version from ~>2 to ~> 3.55.0 (aws provider version 3.55.0 is the first version that supports python 3.9 runtime)
I've seen that others have had similar issues and what seemed to have worked for them is trying a different version of the provider. I wanted to keep these versions of terraform and aws provider because if I upgrade it further here, it would have consequences elsewhere in our pipeline. Does anyone have any ideas on how I can move forward?
I've finally solved it. I increased the Compute resources allocated to Codebuild by following this page: https://docs.aws.amazon.com/codebuild/latest/userguide/change-project-cli.html
All my builds are running through successfully now. So it looks like it was just the resource constraint all along.
I'm creating an ec2 instance using terraform and i have installed all prerequiste on my system, but unfourtunality when i run "terraform init" shown this message "
Initializing provider plugins...
Terraform has been successfully initialized!
but in directory there is no modules initilized and after run terraform plan there is no paln shows and also terraform apply command i receive this one "No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
"
I'm new in this field kindly i need some guide to lunche the ec2 instance
I am trying to run the terraform code and running the terraform init but I am running into issues.
As you can see, when I run with sudo, it has no issues, but without it, it has. I am using mac os Mojave terraform 0.12. I checked the folder permissions and it is just fine.
once I run sudo terraform init, the other commands don't need the sudo command.
Initializing the backend...
Initializing provider plugins...
- Checking for available provider plugins...
Registry service unreachable.
This may indicate a network issue, or an issue with the requested Terraform Registry.
Registry service unreachable.
This may indicate a network issue, or an issue with the requested Terraform Registry.
Error: registry service is unreachable, check https://status.hashicorp.com/ for status updates
Error: registry service is unreachable, check https://status.hashicorp.com/ for status updates
C02Z1BCSLVCG:blue-deployment shakyas$ sudo terraform init
Password:
Initializing the backend...
Initializing provider plugins...
- Checking for available provider plugins...
- Downloading plugin for provider "aws" (hashicorp/aws) 2.42.0...
- Downloading plugin for provider "template" (hashicorp/template) 2.1.2...
The following providers do not have any version constraints in configuration,
so the latest version was installed.
To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.
* provider.aws: version = "~> 2.42"
* provider.template: version = "~> 2.1"
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
I had the same issue, and I resolved it with removing a lot of certificates in my macOS Keychain.
It sound weird and I still don't understand why it works, but it works for others people too : https://discuss.hashicorp.com/t/error-when-running-terraform-init/3135/6
I'm keep getting this error. I have installed heroku toolkit successfully
C:\Users\hp-u>heroku login
Would you like to submit Heroku CLI usage information to better improve the CLI user experience?
[y/N] Y
heroku-cli: Installing core plugins...Error reading plugin heroku-apps.
Reinstalling... Error reading plugin heroku-apps. Reinstalling ... Error reading plugin heroku-apps. Reinstalling
I removed the s from https:// in the value HTTPS_PROXY variable and it worked.
so:
export HTTPS_PROXY="http://myproxy.com:8080"
//instead of
export HTTPS_PROXY="https://myproxy.com:8080"
i.e. somehow the internal college proxy itself might not be able to perform SSL communication