Terraform: How to add version info to custom provider?

[runzexia]

Terraform Version

Terraform v0.11.1

Expected Behavior

provider.qingcloud (v1.1)

Actual Behavior

provider.qingcloud (unversioned)

[jbardin]

Hi @runzexia,

The provider version is determined from the executable file name by appending _v and the semver string.

Naming your provider terraform-provider-qingcloud_v1.1.0 should get you the behavior you're expecting.

I've marked this for documentation, since I don't see the filename versioning mentioned in the custom provider docs.

[apparentlymart]

This is currently mentioned in the _Third-party Plugins_ section, but the audience of that doc is plugin users rather than plugin developers. I think our docs for plugin _developers_ are a bit stale here and mostly date to before we had plugin versioning, so we can find a good place to mention it for developers too.

@runzexia, do you remember which doc pages, if any, you referred to when developing this provider? If you can recall, that will help us decide where is a good place to mention this so that future developers are likely to find it.

[runzexia]

https://www.terraform.io/guides/writing-custom-terraform-providers.html

[apparentlymart]

Thanks @runzexia! I think what we should do here is add a new section to that guide on how to package a custom plugin for distribution, which can mention the naming scheme @jbardin described, along with other distribution-related concerns such as cross-compilation and testing.

[mildwonkey]

The various docs and guide (as well as most of the underlying code) have changed since this issue was opened, so I am going to close it. Thanks!

If there is still a question, I recommend the the community forum, where there are far more people available to help. If there is a bug or you would like to make a feature request, please open a new issue and fill out the template.
Thanks!

[hashibot[bot]]

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.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.