dapr / dapr/components-contrib

extend input bindings with binding expressions to wire up related output bindings

Open
#471 3 comments 0 reactions 0 assignees View on GitHub
area/runtime/binding kind/enhancement P2 pinned
Dominant language
Go
Stars
602
Forks
580
Avg merge
4d 9h
Merged PRs (30d)
6

Description

Azure Functions has this notion of [binding expressions](https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-expressions-patterns) which allows to wire up input bindings (in Azure Functions terminology) with a trigger binding.

C# Sample: Correlation Id or queue message is used to lookup document (large message payload) from Blob Storage:

```
[FunctionName(nameof(DistributeInvoice))]
public static void DistributeInvoice(
[ServiceBusTrigger(
"invoice-queue",
Connection = "sbConnection")] Microsoft.Azure.ServiceBus.Message messageHeader,
[Blob(
"payloads/invoice/{correlationId}",
FileAccess.Read,
Connection = "payloadStorage")] string payloadIn,
ILogger log,
ExecutionContext context)
{
```

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named in the issue. Start by locating the component and binding documentation relevant to input and trigger bindings; done means supporting Azure Functions-style expressions that connect a trigger to an input binding, including the correlation-id/blob-storage example.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.