-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Allow for Custom User Agent Info #9149
Comments
I found TF_APPEND_USER_AGENT in Terraform itself, and was somehow expecting that this would be reflected in providers as well. But according to Would be nice if appending to the user-agent via config or ENV was possible somehow. Could be very useful for https://github.com/hashicorp/terraform-cdk and similar tooling. |
Unfortunately the AWS SDK does not just take a User-Agent string, but requires a more specific construction, so the implementation will need to do a bit more work and parse the string, etc. This is planned to follow the 3.0 release. |
Cool, thanks for elaborating on this 👍 |
Support for this functionality (using the |
This has been released in version 3.3.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
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. Thanks! |
Community Note
Description
The AWS client is currently configured to send information in API requests via the UserAgent field including Terraform version and HashiCorp indentification. I propose allowing for users to provide additional configuration information, such as a deployment agent and job ID if they are using Jenkins or similar products.
I would be happy to do the work required to implement this feature.
New or Affected Resource(s)
This change will not affect the functionality of any AWS resource types.
References
The User Agent field is currently being configured in config.go
The text was updated successfully, but these errors were encountered: