Repository navigation
New x-goog-api-client information for gRPC-based APIs #2019
Description
Activity
- added a commit that references this issue
on Feb 24, 2017 - added
on Feb 24, 2017 - added 2 commits that reference this issue
on Feb 24, 2017 22 remaining items
- added a commit that references this issue
on Mar 9, 2017 Now the code on master has this fully; @stephenplusplus or @callmehiphop -- please push new version of these API clients to npmjs.com, so that further API calls can contain this data.
Reacted by Brian J. WatsonThanks @jmuk!
@stephenplusplus and @callmehiphop please let me know when all of the client libs have been republished with these new headers.
I'll be publishing these tomorrow. It involves a bit more work than expected because of a breaking change in
@google-cloud/common-grpc.All modules have been published.
- added 2 commits that reference this issue
on Oct 11, 2022 - added a commit that references this issue
on Nov 11, 2022 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 11, 2026
(sorry not filed an issue so far); we are going to add x-goog-api-client header info to the gRPC-based APIs in certain format:
"gl-node/(node version) gccl/(library version) grpc/(grpc version)""gl-node/(node version) gccl/(library version) gapic/(autogen version) gax/(gax version) grpc/(grpc version)"Also the gapic autogen files will generate its own http header -- so that if the user chooses to use gapic layer directly, it has the information, but not with
gcclpart. This means we need to regenerate the autogen files too.This issue tracks its progress.
The following APIs will be affected: