Skip to content
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

Grpc: Send context data with ClientGrpc #881

Closed
coderdiaz opened this issue Jul 16, 2018 · 5 comments
Closed

Grpc: Send context data with ClientGrpc #881

coderdiaz opened this issue Jul 16, 2018 · 5 comments

Comments

@coderdiaz
Copy link

coderdiaz commented Jul 16, 2018

I'm submitting a...


[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Actually, I have a microservice based in Golang and I need to request a Grpc Method but this need a Authorization Header.

How can I send this header using the ClientGrpc in Nest?

Expected behavior

Send context data using ClientGrpc implementation.

What is the motivation / use case for changing the behavior?

  • Request methods only with authorization header present.

Environment


Nest version: 5.0.0

 
For Tooling issues:
- Node version: 8.9.0  
- Platform:  Mac 

Others:

- Npm: 5.5.1
@gatero
Copy link

gatero commented Jul 17, 2018

+1

@kamilmysliwiec
Copy link
Member

Pass grpc.Metadata object as a second argument.

@kamilmysliwiec
Copy link
Member

Created issue in the docs repository nestjs/docs.nestjs.com#115

@zodiac1214
Copy link

Pass grpc.Metadata object as a second argument.

https://stackoverflow.com/a/54279876 this is what the "second argument" is ..... :(

@lock
Copy link

lock bot commented Oct 15, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants