-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support external provider binaries that are not built by go #195
Comments
In case you give green light, I can provide a pull request. My Idea would be to introduce a new argument called --provider-path and in case of specifying the argument, the |
Hi @teneko 👋 Thank you for raising this. In general, this seems like a reasonable request and proposed solution, however I have added this to our next team triage meeting to discuss further. We'll let you know afterwards. Thanks again! |
And have you met once in the last 2 months? 😄 |
Since it seems that this issue is being ignored, please consider it unplanned. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Hi. I am author pseudo-dynamic/Terraform.Provider.Scaffolding that is written in C# and uses PseudoDynamic.Terraform.Toolset as provider framework.
I wanted to ask you kindly, whether you would like to support specifying a path to a custom provider binary, so that I can point to the Terraform provider artifact compiled by
dotnet
.For reference: This is the repository I would like to generate a Terraform provider plugin documentation for: pseudo-dynamic/Terraform.Provider.Scaffolding, but this requires an extension to
tfplugindocs
as it seems that thego build
procedure is a fixed part of thetfplugindocs generate
command.So my question is, would you consider to add support for external Terraform plugin provider binaries by supporting specifiying a path pointing to the external Terraform plugin provider?
The text was updated successfully, but these errors were encountered: