dapr / dapr/dotnet-sdk

Enable SDK to call non Dapr http endpoints

Open
#1,501 9 comments 0 reactions 0 assignees View on GitHub
area/client/invoke kind/enhancement
Dominant language
C#
Stars
1.2k
Forks
378
Avg merge
2d 1h
Merged PRs (30d)
6

Description

## Describe the feature
Dapr allows to call non dapr http endpoints based on the [docs](https://docs.dapr.io/developing-applications/building-blocks/service-invocation/howto-invoke-non-dapr-endpoints/). This providers the benefit of being able to apply resiliency policies etc.

This works well for me when using the Dapr API dirctly.
```http
GET http://localhost:3570/v1.0/invoke/https://docs.dapr.io/method/
```

Unfortunately I'm unable to also get this to work with the sdk.
When I see it correctly the `CreateInvokeHttpClient` doesn't provide an overload for the FQND functionality.

Is it possible to enhance the SDK to also enable the http calling of non dapr endpoints?

## Release Note
RELEASE NOTE:
**ADD**: Enable non dapr http endpoint calling

Contributor guide

Open the contributing guide

Research direction

Start with the SDK's CreateInvokeHttpClient entry point and compare its behavior with the Dapr non-Dapr endpoint documentation linked in the issue. Check how the fully qualified endpoint is represented in the direct HTTP example, then verify the SDK can make the same call and preserve the requested endpoint behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.