-
Notifications
You must be signed in to change notification settings - Fork 66
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
Client streaming methods should send routing headers #448
Comments
any updates as we are out of slo |
@busunkim96 , can you clarify why this isn't an issue for libraries using micro-generator? is this a feature gap between micro-generator and the legacy (monolith) that we need to support i.e adding routing headers to the streaming requests? If not, we should mark this bug as feature request or mark with appropriate priority so we can fix it. Please advice. Thanks! P.S: This issue triggered OO-SLO. |
@hkdevandla None of the currently published APIs have a streaming method that requires a routing header be sent. I opened this after discussion #443 which added routing headers for all the http verbs. The current behavior may be correct, but I opened this to make sure this comment was followed up on:
Originally posted by @software-dov in #443 (comment) |
Thanks @busunkim96, making this as P3 in that case if it is not an issue but needs some follow up/investigation. |
We are dropping this to a feature request for the time being. |
Clients streaming methods should send routing headers on the initial RPC that opens the stream. Field headers are currently ignored for these methods
gapic-generator-python/gapic/templates/%namespace/%name_%version/%sub/services/%service/client.py.j2
Lines 329 to 341 in eaa6f36
As far as I know this isn't currently an issue for any libraries on the microgenerator.
The text was updated successfully, but these errors were encountered: