Closed fgheysels closed 3 years ago
It looks like the custom setting name on the output binding on IAsyncCollector works with the custom settingname.
When I call the SubscribeToDeviceAsync
method however, which has the SignalRTrigger
binding, I get the response:
Microsoft.AspNetCore.SignalR.HubException: 'The SignalR Service connection string or endpoints are not set.'
As soon as I change the SignalRTrigger binding (remove the ConnectionStringSetting
property-name and add a setting AzureSignalRConnectionString
to my Function configuration, the function works as expected.
ConnectionStringSetting
for SignalRTrigger
should work in traditional mode, like the sample you give. I am unable to reproduce the problem. Could you give a reproducible function project?
Already reproduced the problem. invocationContext.GetGroupsAsync()
method doesn't respect the ConnectionStringSetting
. Will fix later.
I've created an Azure Function which has bindings to a serverless Azure SignalR resource. In the Azure SignalR resource, I've configured 'Upstream' to my Azure Function.
The Azure Function App contains multiple functions which have SignalR triggers or SignalR outputs, like this:
or
Note that I've specified a custom setting-name for the SignalR connectionstring setting (as is documented here ) When I run my Function, I get InvalidOperationExceptions which say:
When I remove the
ConnectionStringSetting
from my bindings, and configure the function to have a setting namedAzureSignalRConnectionString
, then everything works.