[gRPC] Is it possible to have environment variables in paths?
See original GitHub issueI need to do something like the following:
proto < $GOPATH/my-service/my-service.proto
enums: String,
###
GRPC http://localhost:9090/myservice.MyService/GetUser
{
"userId": "123456",
}
How can I achieve this?
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
grpc/environment_variables.md at master - GitHub
gRPC C core based implementations (those contained in this repository) expose some configuration as environment variables that can be set.
Read more >How to set environment variable LD_LIBRARY_PATH through ...
I am using protobuf gradle plugin in my build. gradle file to generate grpc and reactor gprc java code. Due to the security...
Read more >Use environment variables | Cloud Run Documentation
When you set environment variables, they are injected into the container and are accessible to your code. Environment variables are set as key/value...
Read more >Consuming a gRPC Service - Quarkus
The classpath path or file path to a server certificate or certificate chain in PEM format. Environment variable: QUARKUS_GRPC_CLIENTS__CLIENT_NAME__ ...
Read more >How to Interact With and Debug a gRPC Server - Medium
You can troubleshoot and change how C gRPC works by setting a few environment variables. There is a more complete reference of these...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
With the new version it is now possible to use variables.
System environment variables can be used with
process.env.GOPATH
Thanks for the idea.
That’s right, the env variables depends on how you launch VSCode. If I launch it using the
code
command, it works.I found an issue related to this behaviour and apparently this is expected. I think I will avoid shell env variables and rely on constants defined within the httpyac environment.
Thank you for the support and the great tool!