ServiceBusTrigger and ServiceBus outpub binding in a transaction

[SeanFeldman]

Azure Service Bus supports a transactional processing of an incoming message with emitting the outgoing messages using TransactionScope and Send-Via feature.

As of today (using Functions 2.0 / WebJobs 3.0) there's no way to achieve this as ServiceBusTrigger and ServiceBusAttribute used for collectors do not share the same ServiceBusConnection.

1. Is this going to be supported?
2. While the support for transactional messaging is not there, is there a way to get access to the receiver's connection to be used from the function to emit messages bypassing collector?

[alrod]

1. We do not have plans to support TransactionScope.
2. You can access MessageReceiver inside your function app code:
   

   azure-webjobs-sdk/test/Microsoft.Azure.WebJobs.Host.EndToEndTests/ServiceBusEndToEndTests.cs

   Line 378 in f386e54

   MessageReceiver messageReceiver,

[SeanFeldman]

@alrod thank you.

Just before I close this issue, is there a documented list of things that are available for injection for Service Bus trigger? MessageReceiver is there, but if I try to inject IClientEntity, it fails. I'd rather look it up in the documentation than raise an issue each time. Thank you.

[alrod]

It looks like we do not have the full list in the docs. The only list I found is message properties:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus#trigger---message-metadata

You can find full list here:

azure-webjobs-sdk/src/Microsoft.Azure.WebJobs.Extensions.ServiceBus/Triggers/ServiceBusTriggerBinding.cs

Line 142 in 2e374a2

internal static IReadOnlyDictionary<string, object> CreateBindingData(Message value, MessageReceiver receiver, IReadOnlyDictionary<string, object> bindingDataFromValueType)

[SeanFeldman]

That is peculiar. I've raised a doco issue (https://github.com/MicrosoftDocs/azure-docs/issues/32126) to point that out. Would be nice have MessageReader in the context of the output binding, but affraid the modular design will not allow it. If you have two output bindings with two different namespaces, this would not work.
Thank you @alrod.

[SeanFeldman]

You will hate me, but one more question - when using MessageReceiver to perform a transactional send from a Function, the incoming message must be completed within the transaction scope. Which is against the Functions design, assuming SDK has to complete the incoming message. It's not a biggie, but will cause the host to log a nasty exception for no good reason:

Is there a way to suppress it or indicated to the SDK that a function will take care of the message completion? I don't recall anything like that in the Functions doco. Need memory implants ASAP.

[alrod]

https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus#hostjson-settings
"autoComplete": false

[SeanFeldman]

🤦‍♂️ Fantastic, thank you!