-
Notifications
You must be signed in to change notification settings - Fork 143
Developing the Provider #149
Comments
Place in your provider_installation {
filesystem_mirror {
path = "/usr/share/.terraform.d/providers"
include = ["terraform.local/*/*"]
}
direct {
exclude = ["terraform.local/*/*"]
}
} Place your binary (depending on your OS and ARCH) in Use in terraform config: terraform {
required_providers {
myplugin= {
source = "terraform.local/local/myplugin"
version = "~> 1.0.0"
}
}
} Keep in mind you may encounter unknown errors while using a module that points to provider with the same name but different binary (even if they're exactly same binaries even with matching checksum/hash). |
Thanks @bukowa ! That's just the info I was looking for. Would be super useful to get that added to the bottom of the README if you're up for PR-ing it :) (I'm part of Hashi, but this ain't my team) |
Hey there's also nice |
Hi folks 👋 In addition to manually copying the provider binary for local installation into a conventional directory, you can also use the Additional references:
|
I was looking at If I'm understanding your comment, and that second link, then it's as simple as...
Nice! That makes things MUCH easier :D (I'd seen https://www.terraform.io/plugin/debugging, but I'd not seen the https://learn.hashicorp.com link before. That's super helpful) So then, I think it makes sense for us to reference that page in this repo's README file |
Hey, I cannot find any information about actually using this provider in my configuration files.
For ex. after building the binary what should I do now to use that provider in my terraform config without actually publishing it into registry?
hashicorp/terraform#25906
hashicorp/terraform#26123
https://discuss.hashicorp.com/t/easiest-way-to-use-a-local-custom-provider-with-terraform-0-13/12691
The text was updated successfully, but these errors were encountered: