funopk.blogg.se

The mechanics of provider installation changed in Terraform 0.13, thanks to the introduction of the Terraform Registry for providers which allows custom and community providers to be installed via terraform init. In rare cases, it might also be necessary to install extra software on the Terraform worker, such as a configuration management tool or cloud CLI. In most cases, Terraform can automatically download the required plugins, but there are cases where plugins must be managed explicitly. Terraform relies on provider plugins to manage resources. If you're already running VS Code then reload it Go to the Command Palette (Ctrl+Shift+P) and type reload, then select reload window Then once vs code restarts, wait a bit for the language server to start.įor example type resource "aws_ and you should see the auto-complete options.Īlso inside a resources block like "aws_vpc" if you hit you should see the available options, like cidr_block.»Installing Software in the Run Environment Make sure you have the AWS provider executable in these folders:Ĭ:\Users\\.vscode\extensions\mauve.terraform-1.4.0\lspbin\Ĭ:\Users\\.vscode\extensions\mauve.terraform-1.4.0\lspbin\.terraform\plugins\windows_amd64 You can get the executable by running Terraform init by the way or by manually downloading it from here: I'm currently using this version: terraform-provider-aws_v2.38.0_x4.exe

My Setup: I'm using Windbuild 18362.476 with VS Code 1.40.1 and the extension mauve.terraform 1.4.0Įnable the Terraform Language Server in settings.json like so: "terraform.languageServer": in the providers.tf file here: C:\Users\\.vscode\extensions\mauve.terraform-1.4.0\lspbin\providers.tf

So I've been fighting with VS Code to make the Terraform extension work for AWS for Terraform v0.12Īfter a couple of hours I think I have it working, so for anyone else that might have the same problem I thought I'd make this post.