I'm currently developing a TypeScript Azure Function that utilizes an Azure Service Bus topic as its output. Although I am able to send messages successfully, I have encountered difficulties in setting custom metadata properties for the message.
In my attempts to resolve this issue, I experimented with an object resembling the interface of the ServiceBusMessage from the Service Bus Javascript SDK, similar to the following code:
import { AzureFunction, Context, HttpRequest } from "@azure/functions";
const httpTrigger: AzureFunction = async function (
context: Context,
req: HttpRequest
): Promise<void> {
const message = {
body: "my message content",
applicationProperties: { key: "value" },
};
context.bindings.myTopic = message;
};
export default httpTrigger;
Unfortunately, when the message is sent, it remains unaltered and the applicationProperties values are disregarded. As a result, I cannot view these properties on the Azure Portal within the Service Bus Explorer. Furthermore, the message's content will be displayed as the JSON representation of the message object.
I also attempted using extension bundles 3 and 4, but was unsuccessful in resolving the issue.
To provide further context, here's the contents of my function.json file:
{
"bindings": [
{
"authLevel": "function",
"type": "httpTrigger",
"direction": "in",
"name": "req",
"methods": ["get", "post"]
},
{
"type": "http",
"direction": "out",
"name": "res"
},
{
"name": "myTopic",
"type": "serviceBus",
"queueName": "myTopic",
"connection": "SERVICE_BUS_CONNECTION_STRING",
"direction": "out"
}
],
"scriptFile": "../dist/servicebus-writer/index.js"
}
And my host.json file:
{
"version": "2.0",
"logging": {
"applicationInsights": {
"samplingSettings": {
"isEnabled": true,
"excludedTypes": "Request"
}
}
},
"extensionBundle": {
"id": "Microsoft.Azure.Functions.ExtensionBundle",
"version": "[3.3.0, 4.0.0)"
}
}
At this point, I would greatly appreciate any assistance in resolving this issue and learning how to properly set custom properties for my messages.