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

Support DAPR_HTTP_ENDPOINT and/or DAPR_GRPC_ENDPOINT #415

Open
artursouza opened this issue Jun 12, 2023 · 1 comment
Open

Support DAPR_HTTP_ENDPOINT and/or DAPR_GRPC_ENDPOINT #415

artursouza opened this issue Jun 12, 2023 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@artursouza
Copy link
Member

Describe the proposal

Allow consistent way to configure endpoint for Dapr's sidecar, while enabling remote sidecar configuration.

Child of dapr/dapr#6035

SDK should parse these in a consistent way, so operators have a consistent environment variable to set for Dapr apps. Right now, each SDK has their own way of configuring the endpoint for Dapr's sidecar.

If SDK allows gRPC communication from SDK to sidecar, then DAPR_GRPC_ENDPOINT must be supported.
If SDK allows HTTP communication from SDK to sidecar, then DAPR_HTTP_ENDPOINT must be supported.
DAPR_HTTP_ENDPOINT and DAPR_GRPC_ENDPOINT and not exclusive, meaning it is acceptable to support both, like in the Java SDK, if the SDK supports both protocols.
Also, companies might decide to offer different endpoints per protocol, so there is not an unique environment variable for both.

@artursouza artursouza added the enhancement New feature or request label Jun 12, 2023
@mikeee mikeee added the good first issue Good for newcomers label Feb 20, 2024
@yanleiwang
Copy link

I'm new here, and I'd like to know if this issue has been resolved by https://github.com/dapr/go-sdk/pull/475
If not, can you tell me roughly what I need to do, and please assign this task to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
No open projects
Development

No branches or pull requests

3 participants