So to sum this up, the commands to copy the provider in the right directory for macOS are: mkdir -p ~ /Library/Application \ Support/io.terraform/plugins//honeycombio/99.0.0/darwin_amd64/Ĭp terraform-provider-honeycombio_99.0.0 ~ /Library/Application \ Support/io.terraform/plugins//kvrhdn/honeycombio/99.0. The OS/arch string can be retrieved using $(go env GOOS)_$(go env GOARCH): # on macOS In the case of the honeycombio provider (on macOS) that would be: /kvrhdn/honeycombio/99.0.0/darwin_amd64/ Within the plugins directory, the providers are organized in a directory structure using the following format: ///// The best way to understand what Terraform can enable for your infrastructure is to see it in action. In the case of macOS this is ~/Library/Application Support/io.terraform/plugins. This directory differs per OS as documented here. The easiest way to install a provider with Terraform 0.13 is to place it in a local mirror directory. We use the version 99.0.0 to ensure the version of our custom-built provider is higher than any other existing version published on the Terraform registry. This will build an executable that can be used by Terraform. Go build -o terraform-provider-honeycombio_99.0.0. With Go installed, clone the repository and build an executable: git clone Most providers are written Go, in this case you can simply follow the following instructions. A provider is distributed as binary and should be named in the following format: terraform-provider-_įor example, v0.1.0 of the honeycombio provider is named: terraform-provider-honeycombio_0.1.0 To find out how to build your provider, resort to the documentation within its repository. In this blogpost I'll use my honeycomb.io Terraform provider ( kvrhdn/honeycombio) as example, but the instructions should be similar for other providers. I found it surprisingly difficult to install a provider without using the registry, hence why I decided to document and share my steps. Unfortunately, this has also made it more difficult to use a provider that is not published on the registry. With Terraform 0.13 it's now significantly easier to use community developed providers: include it in your configuration and Terraform will install the provider automatically from the Terraform Registry.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |