-
Notifications
You must be signed in to change notification settings - Fork 494
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
Azure Functions as output binding #1573
Comments
Can't this be done with an HTTP binding? |
Exactly. You'd just use the HTTP binding to call Azure Functions (can have a private API key as query string param). I do not think this component is necessary. Thoughts @artursouza ? |
What about the different auth solutions for Azure? That would need a component to support those, right? |
Also, could we enable the call without requiring a webhook if we use the Azure SDK? |
You can't invoke functions using an SDK, the HTTP endpoint is the only way, and auth is defined on the endpoint. |
At this point, Azure Functions can only be invoked with a Webhook that (when not anonymous) uses auth via a shared secret. I don't believe there's support for AAD auth (unless that gets implemented as part of the Function code by the user). However, that would be a good thing to ask the Functions team. There's certainly value in exploring stronger auth for Functions. |
Closing this issue as there is nothing that can be implemented. |
@berndverst releated proposal: dapr/proposals#16 |
Describe the proposal
Create a new binding component that will trigger a function in Azure Functions
The text was updated successfully, but these errors were encountered: