-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add new version.go file + linker flags. #2438
Add new version.go file + linker flags. #2438
Conversation
Make sure the user agent changes fit in with the work @ndmckinley is doing with user agents. |
Yep! He'll be the reviewer on the MM-side PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. We didn't do anything special in the building scripts to differentiate providers, it didn't hurt the build to define flags that aren't used. So it should just start picking this up on new releases.
Thanks Paul! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Hey Paul!
We're interested in getting the binary version of the Google provider(s) in our user agent strings, similar to the change you made in hashicorp/terraform-provider-azurerm#2032.
Your comment mentions that the version is set during the release process. Is that something that we automatically pick up across
google
andgoogle-beta
with similar changes, or will you/ @paddycarver need to do something manual on your side?This PR sets up the
version.go
file, I've made a PR with Magic Modules to exclude that file from our generation, and I'll send a PR using the new value as a followup (unfortunately, I think I can only send out that PR after this one lands because we only generate if the provider can successfully build).