-
Notifications
You must be signed in to change notification settings - Fork 69
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
Routing headers are not passed to the operations client #732
Comments
FWIW the Go GAPICs use an LRO GAPIC under the hood. The LRO GAPIC is made using the google/longrunning/operations.proto which have |
I understand why it may require |
I had the same thought last night. I think you are right, @alexander-fenster, passing the value of the I think This could be straight forward as passing the |
OK, thank you @noahdietz – then for TypeScript it's just a quick fix to the operations client that is in google-gax (it was originally a generated GAPIC but never updated, for some reason it does not pass |
I think I can just make this fix in Python's gax then - |
See internal issue 173104871 for more details.
Some APIs require routing headers (location info in
x-goog-request-params
) for successful requests. https://google.aip.dev/client-libraries/4222gapic-generator-python/gapic/templates/%namespace/%name_%version/%sub/services/%service/client.py.j2
Lines 412 to 435 in e5b7648
These headers are added to normal requests to the API but are missing in calls to the Operations API. This results in requests failing with permission denied errors.
gapic-generator-python/gapic/templates/%namespace/%name_%version/%sub/services/%service/client.py.j2
Lines 436 to 444 in e5b7648
A fix will require:
google-api-core
with an operations client that accepts and uses gRPC metadataThe text was updated successfully, but these errors were encountered: