-
Notifications
You must be signed in to change notification settings - Fork 12
Submit provider to Terraform Registry #238
Comments
Hi @suzuki-shunsuke , I would like to ask if you plan to publish to the Terraform registry or not. We would love to use the module and use it from the registry as it's super easy and I would rather see this package published by you than fork it and do own release... Many thanks for answer! |
Sorry for late reply. I try to publish this provider from https://registry.terraform.io/ . But it seems that we can publish not https://registry.terraform.io/github/create And I can't select this repository due to the repository name's restriction. https://www.terraform.io/docs/registry/modules/publish.html#requirements
|
By the way, a few months ago I requested to add this provider to the community providers list, but there was no reply from Hashicorp...
https://www.terraform.io/docs/providers/type/community-index.html |
@suzuki-shunsuke It looks like your Graylog provider is already on the providers list, but it just links back to this repo. |
Oh, I didn't know! Thank you!! I read the issue hashicorp/terraform#15252 , |
Not an actual issue per say, but more of a request:
I found this Graylog provider to be very useful in our CI workflows. The only wrinkle in setting this up is that we have to reach out and download the provider before doing a
terraform init
and point the plugin path to some directory where we store the provider binary.Can you try to submit this to the official Terraform repository so that users of this provider can have the all of the documentation, files, and other info in a single location from Terraform instead of linking back to this repo?
https://www.terraform.io/docs/registry/providers/docs.html
The text was updated successfully, but these errors were encountered: