You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working with async functions and trying to publish events using the Dapr APIs is impossible with the current setup.
Currently, dapr sidecars are started with app-protocol grpc. This limits the connections to deliver events to the application to have a grpc endpoint that requires a bidirectional connection to be open between the function and the sidecar.
This is a problem because the function might be downscaled (and even if the mode is set to standalone, the channel will be closed).
Allowing HTTP app-protocol will enable the dapr sidecar to send an http requests to the function that will work even if the function was downscaled.
The text was updated successfully, but these errors were encountered:
You can configure the Dapr sidecar’s protocol by setting the annotations in OpenFunction. The annotation is: dapr.io/app-protocol: http. This will allow you to use the Dapr API to publish events to asynchronous functions.
Description
Working with async functions and trying to publish events using the Dapr APIs is impossible with the current setup.
Currently, dapr sidecars are started with app-protocol
grpc
. This limits the connections to deliver events to the application to have a grpc endpoint that requires a bidirectional connection to be open between the function and the sidecar.This is a problem because the function might be downscaled (and even if the mode is set to standalone, the channel will be closed).
Allowing HTTP app-protocol will enable the dapr sidecar to send an http requests to the function that will work even if the function was downscaled.
The text was updated successfully, but these errors were encountered: