![]() ![]() ![]() chmod +x ~/.terraform.d/plugins/linux_amd64/terraform-provider-elasticsearch_v1.0.0 This is really important since it associates the version = "X.Y.Z" in the terraform provider code with the actual binary (It’s possible to have multiple versions of the same binary in your plugins folder).įinally don’t forget to set the binary file as executable. ![]() ![]() Also, we are naming the binary with the terraform-provider-_vX.Y.Z format. Notice that we are outputting the binary to the ~/.terraform.d/plugins/linux_amd64/ directory. curl -sL -output ~/.terraform.d/plugins/linux_amd64/terraform-provider-elasticsearch_v1.0.0 Most providers will expose their software packages via github releases, so that’s the place to look for the right binary for your architecture. If you are running a different operating system architecture please use the documentation to find the right one for you. Right now, I’m running Terraform on a linux machine, therefore the need for the linux_amd64 directory. mkdir -p ~/.terraform.d/plugins/linux_amd64 To allow the use of external plugins we will need to create the plugins directory. Whenever you installed terraform, a ~/.terraform.d/ directory was created. We will be installing the phillbaker / terraform-provider-elasticsearch as an example. In this post I will be showing you the quickest way of installing external plugins in terraform, without the need to dig deep into Terraform’s docs. That’s great, but soon enough you’ll need to use some provider that does not work out of the box by running terraform init. Hashicorp already distributes plugins that it maintains along with the community ( check them here), for instance, aws. How to install third-party plugins in Terraform How to install third-party plugins in Terraform - dimmaski ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |