In our ASP.NET Core hosts we have send-only endpoints, and in cases where we need to perform database write operations in combination with message sending (via Azure Service Bus) I was planning to use this package to provide an Outbox-like feature.
When I start the connector (without any fancy configuration, atleast) it requires queues to be created in the connected transport (Azure Service Bus). Seeing as these endpoints are send-only, is there a way to configure the connector to not require queues to exist in the connected transport?
My scenario is similar to what is discussed here.
In our ASP.NET Core hosts we have send-only endpoints, and in cases where we need to perform database write operations in combination with message sending (via Azure Service Bus) I was planning to use this package to provide an Outbox-like feature.
When I start the connector (without any fancy configuration, atleast) it requires queues to be created in the connected transport (Azure Service Bus). Seeing as these endpoints are send-only, is there a way to configure the connector to not require queues to exist in the connected transport?