terraform/pluginsģ 20:30:37 getproviders.SearchLocalDirectory: found vmc.nico/edu/nsxt v3.2.0 for darwin_amd64 at. Finding latest version of vmc.nico/edu/nsxt.ģ 20:30:37 providercache.fillMetaCache: scanning directory. terraform/pluginsģ 20:30:37 : installing vmc.nico/edu/nsxt v3.2.0 from /Users/nicolasvibert/.terraform.d/plugins/vmc.nico/edu/nsxt/3.2/darwin_amd64 Nicolasvibert$ TF_LOG=trace terraform initģ 19:59:38 Terraform version: 0.13.0ģ 19:59:38 Go runtime version: go1.14.7ģ 19:59:38 will search for provider plugins in /Users/nicolasvibert/.terraform.d/pluginsģ 19:59:38 getproviders.SearchLocalDirectory: found vmc.nico/edu/nsxt v3.2.0 for darwin_amd64 at /Users/nicolasvibert/.terraform.d/plugins/vmc.nico/edu/nsxt/3.2/darwin_amd64ģ 19:59:38 providercache.fillMetaCache: scanning directory. I create a folder (the path of the folder is important here) and move the provider to the newly created folder. It turned out the “ required_providers” could also work for in-house providers and for those located on my hard drive.įirst, I had to move the compiled provider (always named something like terraform-provider-something) to the right folder – it has to be in the user plugins directory, located at ~/.terraform.d/plugins on most operating systems and %APPDATA%\terraform.d\plugins on Windows.
Terraform plugins how to#
I downloaded the code from GitHub, compiled it (I explained how to do this here) but ran into some issues as I couldn’t find a way to force Terraform to use the one provided from GitHub – instead, it kept downloading the official one on the registry instead of using the prototype I had downloaded and compiled from GitHub.
Our developers implemented the change and asked me to test the prototype. A recent example was when one of my customers required a minor improvement on the Terraform for NSX-T Policy Provider. While the above was great for a provider that is publicly available, there are times when providers are still private or cannot be published on the registry yet. Terraform for VeloCloud In-house providers I was able to create a VMware SD-WAN edge as you can see in the brief demo below. This short command worked as I had hoped and so did Antoine’s experimental provider. For “ adeleporte/velocloud“, Terraform will check the Terraform Registry for a “ velocloud” provider registered under the “ adeleporte” username.
Terraform plugins install#
If, for example, your file includes “ provider aws“, Terraform will deduce it has to download the Terraform AWS provider before it tries to deploy AWS resources.įor providers distributed by HashiCorp, init will automatically download from the Terraform Registry and install plugins if necessary.īut what if you want to use an experimental provider? Or want to leverage one that is not officially provided by HashiCorp? How can you specify the provider you require?īy using “provider requirements” and the “ required_providers” keyword!īy default, when you define the source as field1/field2, Terraform will look at the user field1 and the provider field2 on the official Terraform Registry. When you run a “ terraform init” command, a number of things happened, as documented in the official documentation.ĭuring init, Terraform checks the configuration of configuration files (.tf files – main.tf in most of my examples) for direct and indirect references to providers and attempts to load the required plugins. One of the first actions before you deploy resources with Terraform is to initialize Terraform with “ terraform init“. Let’s review first the challenges we sometimes come across with Terraform. This blog post would have saved me hours (yes, literally hours) of work if a feature had been documented a bit more clearly… I hope it will help readers save some time too!
0 kommentar(er)
