Microsoft.Azure.Functions.Worker.Extensions.WebPubSub
1.7.0-beta.1
Prefix Reserved
See the version list below for details.
dotnet add package Microsoft.Azure.Functions.Worker.Extensions.WebPubSub --version 1.7.0-beta.1
NuGet\Install-Package Microsoft.Azure.Functions.Worker.Extensions.WebPubSub -Version 1.7.0-beta.1
<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.WebPubSub" Version="1.7.0-beta.1" />
paket add Microsoft.Azure.Functions.Worker.Extensions.WebPubSub --version 1.7.0-beta.1
#r "nuget: Microsoft.Azure.Functions.Worker.Extensions.WebPubSub, 1.7.0-beta.1"
// Install Microsoft.Azure.Functions.Worker.Extensions.WebPubSub as a Cake Addin #addin nuget:?package=Microsoft.Azure.Functions.Worker.Extensions.WebPubSub&version=1.7.0-beta.1&prerelease // Install Microsoft.Azure.Functions.Worker.Extensions.WebPubSub as a Cake Tool #tool nuget:?package=Microsoft.Azure.Functions.Worker.Extensions.WebPubSub&version=1.7.0-beta.1&prerelease
Azure Web PubSub extension of isolated-process Azure Functions client library for .NET
This extension defines the binding types and triggers in the .NET isolated worker process for Azure Functions, allowing you to write functions that respond to any event published to Web PubSub.
Source code | Package | API reference documentation | Product documentation | Samples
Getting started
Install the package
Install the client library from NuGet:
dotnet add package Microsoft.Azure.Functions.Worker.Extensions.WebPubSub --prerelease
Prerequisites
You must have an Azure subscription and an Azure resource group with a Web PubSub resource. Follow this step-by-step tutorial to create an Azure Web PubSub instance.
Authenticate the client
In order to let the extension work with Azure Web PubSub service, you will need to provide a valid ConnectionString
.
You can find the Keys for you Azure Web PubSub service in the Azure Portal.
The AzureWebJobsStorage
connection string is used to preserve the processing checkpoint information as required refer to Storage considerations
For the local development use the local.settings.json
file to store the connection string, <connection-string>
can be set to WebPubSubConnectionString
as default supported in the extension, or you can set customized names by mapping it with Connection = <connection-string>
in function binding attributes:
{
"Values": {
"AzureWebJobsStorage": "UseDevelopmentStorage=true",
"<connection-string>": "Endpoint=https://<webpubsub-name>.webpubsub.azure.com;AccessKey=<access-key>;Version=1.0;"
}
}
When deployed use the application settings to set the connection string.
Key concepts
Using Web PubSub input binding
Please follow the input binding tutorial to learn about using this extension for building WebPubSubConnection
to create Websockets connection to service with input binding.
Using Web PubSub output binding
Please follow the output binding tutorial to learn about using this extension for publishing Web PubSub messages.
Using Web PubSub trigger
Please follow the trigger binding tutorial to learn about triggering an Azure Function when an event is sent from service upstream.
In Connect
and UserEvent
events, function will respect return values to send back service. Then service will depend on the response to proceed the request or else. The responses and events are paired. For example, Connect
will only respect ConnectEventResponse
or EventErrorResponse
, and ignore other returns. When EventErrorResponse
is returned, service will drop client connection.
Examples
Functions that uses Web PubSub input binding
Use WebPubSubConnectionInput
to build the client negotiate URL.
[Function("Negotiate")]
public static HttpResponseData Run([HttpTrigger(AuthorizationLevel.Anonymous)] HttpRequestData req,
[WebPubSubConnectionInput(Hub = "<web_pubsub_hub>", Connection = "<web_pubsub_connection_name>")] WebPubSubConnection connectionInfo)
{
var response = req.CreateResponse(HttpStatusCode.OK);
response.WriteAsJsonAsync(connectionInfo);
return response;
}
Use WebPubSubContextInput
to read Web PubSub request under HttpTrigger
. This is useful when work with Static Web Apps which supports HttpTrigger
functions only.
// validate method when upstream set as http://<func-host>/api/{event}
[Function("validate")]
public static HttpResponseData Validate(
[HttpTrigger(AuthorizationLevel.Anonymous, "options")] HttpRequestData req,
[WebPubSubContextInput] WebPubSubContext wpsReq)
{
return BuildHttpResponseData(req, wpsReq.Response);
}
// Respond AbuseProtection to put header correctly.
private static HttpResponseData BuildHttpResponseData(HttpRequestData request, SimpleResponse wpsResponse)
{
var response = request.CreateResponse();
response.StatusCode = (HttpStatusCode)wpsResponse.Status;
response.Body = response.Body;
foreach (var header in wpsResponse.Headers)
{
response.Headers.Add(header.Key, header.Value);
}
return response;
}
Functions that uses Web PubSub output binding
[Function("Notification")]
[WebPubSubOutput(Hub = "<web_pubsub_hub>", Connection = "<web_pubsub_connection_name>")]
public static WebPubSubAction Run([HttpTrigger(AuthorizationLevel.Function, "get", "post")] HttpRequestData req)
{
return new SendToAllAction
{
Data = BinaryData.FromString($"Hello SendToAll."),
DataType = WebPubSubDataType.Text
};
}
Functions that uses Web PubSub trigger
[Function("Broadcast")]
public static UserEventResponse Run(
[WebPubSubTrigger("<web_pubsub_hub>", WebPubSubEventType.User, "message")] UserEventRequest request)
{
return new UserEventResponse("[SYSTEM ACK] Received.");
}
For more details see the samples README.
Troubleshooting
Please refer to Monitor Azure Functions for troubleshooting guidance.
Next steps
Read the introduction to Azure Function or creating an Azure Function guide.
Contributing
See our CONTRIBUTING.md for details on building, testing, and contributing to this library.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit cla.microsoft.com.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Microsoft.Azure.Functions.Worker.Extensions.Abstractions (>= 1.1.0)
- System.Memory.Data (>= 1.0.2)
- System.Text.Json (>= 4.7.2)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.7.0 | 8,905 | 7/4/2024 |
1.7.0-beta.1 | 12,090 | 9/15/2023 |
1.5.0-beta.1 | 3,443 | 5/4/2023 |