-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
Provider versioning support #58
Comments
👋 Hi @mairamaa , I don't think there's actually anything for me to do here. Last time I looked this is all about the filename of the provider, rather than embedding the information in the binary. For instance ... if you have installed the provider at
Given that I release the binary as |
Hi and thanks for getting back to me. Yeah, it's the filename that determines the "versioning". Wouldn't the correct place for the actual versioning information be in the binary that is compressed within the packaged versions? Currently the actual binaries are just named as "terraform-provider-kafka" if extracted directly. Could the release script be changed so that it adds the version information to the binary? |
I've updated the release script to include the version in the binary |
Terraform provides a way to constraint provider versions, but this requires plugin filename to end with version number in the format "_vx.y.z". Usage is explained in detail in https://www.terraform.io/docs/configuration/providers.html#plugin-names-and-versions. Feature can then be used within modules by applying constraints such as:
See https://www.terraform.io/docs/configuration/providers.html#version-provider-versions for more details
This is especially useful in cases where Terraform versions are upgraded within organizations and where custom providers require manual installations, as old plugin versions are not necessarily compatible with the new Terraform release.
Currently Kafka provider version is displayed as follows, which prevents usage of versioning constraint:
Kindly requesting that versioning support is added as part of the provider
The text was updated successfully, but these errors were encountered: