Azure Servicebus connector. Topics en Queues #127

Open
opened 2026-08-14 14:49:48 +00:00 by meshflows · 7 comments
Owner

Laten we dan toch maar eens starten aan een bijna native support van de Azure servicebus!

Laten we dan toch maar eens starten aan een bijna native support van de Azure servicebus!
Contributor

@meshflows Voor Azure Service Bus: wat is de eerste slice die je wilt — alleen queues, of ook topics/subscriptions — en hoe hoog staat dit t.o.v. de andere open tickets?

@meshflows Voor Azure Service Bus: wat is de **eerste slice** die je wilt — alleen queues, of ook topics/subscriptions — en hoe hoog staat dit t.o.v. de andere open tickets?
Author
Owner

Topics heeft de hoogste prio. Prio voor #47, #128, #135, #133 Dus redelijk hoog

Topics heeft de hoogste prio. Prio voor #47, #128, #135, #133 Dus redelijk hoog
Contributor

Oppakken: eerste slice = Azure Service Bus Topics (publish).

Branch: feat/issue-127-service-bus-topics

Scope van deze slice (niet de hele epic):

  • capability provider egress-azure-servicebus
  • connection type + secret-ref
  • egress.azure.servicebus.topic.publish (send naar een topic)
  • demo workflow + docs + deploy-wiring

Bewust later (ticket blijft open):

  • queues
  • subscriptions / native triggers
  • peek-lock + complete
  • Logic Apps importer native mapping (blijft AMQP tot triggers er zijn)

@meshflows

Oppakken: **eerste slice = Azure Service Bus Topics (publish)**. Branch: `feat/issue-127-service-bus-topics` Scope van deze slice (niet de hele epic): - capability provider `egress-azure-servicebus` - connection type + secret-ref - `egress.azure.servicebus.topic.publish` (send naar een topic) - demo workflow + docs + deploy-wiring Bewust later (ticket blijft open): - queues - subscriptions / native triggers - peek-lock + complete - Logic Apps importer native mapping (blijft AMQP tot triggers er zijn) @meshflows
Contributor

Voortgang #127 (Topics-slice, niet sluiten — queues blijven open):

ADR-0015 optie C is geimplementeerd, gespiegeld aan AMQP/rabbitmq-trigger-subscriber.

  • Branch: feat/issue-127-service-bus-topics
  • Commits: d0e0468 (publish + peek-lock/complete) + 27b47a7 (trigger subscriber)
  • Image egress-azure-servicebus, tweede deployment azure-servicebus-trigger-subscriber
  • Peek-lock → POST /invoke/azure-servicebus of /dispatch → complete op 2xx, abandon op fout, DLQ na N
  • Start contract: invocation.type: azure_servicebus

PR volgt als CI groen is.

@meshflows

Voortgang #127 (Topics-slice, **niet sluiten** — queues blijven open): **ADR-0015 optie C** is geimplementeerd, gespiegeld aan AMQP/`rabbitmq-trigger-subscriber`. - Branch: `feat/issue-127-service-bus-topics` - Commits: `d0e0468` (publish + peek-lock/complete) + `27b47a7` (trigger subscriber) - Image `egress-azure-servicebus`, tweede deployment `azure-servicebus-trigger-subscriber` - Peek-lock → `POST /invoke/azure-servicebus` of `/dispatch` → complete op 2xx, abandon op fout, DLQ na N - Start contract: `invocation.type: azure_servicebus` PR volgt als CI groen is. @meshflows
Contributor

Gemerged (Topics-slice, ticket blijft open voor queues):

@meshflows

Gemerged (Topics-slice, ticket blijft open voor **queues**): - PR #143: https://code.meshflows.org/MeshFlowsGPL/meshflows/pulls/143 - Productversie #144: ``0.4.0`` — https://code.meshflows.org/MeshFlowsGPL/meshflows/pulls/144 @meshflows
Contributor

Status update - 2026-08-18

The first Azure Service Bus implementation slice is now merged to main.

Shipped

  • Topic publish.
  • Topic subscription peek-lock receive, complete, abandon, and dead-letter.
  • Queue send and receive.
  • Queue peek-lock complete, abandon, and dead-letter.
  • Topic subscription triggers with subscriber-owned settlement.
  • Queue triggers with subscriber-owned settlement.
  • Dashboard trigger picker entries for:
    • Azure Service Bus Topic subscription
    • Azure Service Bus Queue
  • Trigger-owned source configuration:
    • servicebus.topic + servicebus.subscription
    • servicebus.queue
  • Declarative Service Bus entity validation.
  • Dry-run-first reconciliation for enabled topic subscriptions.
  • DSAV SQL rule derivation and removal of the catch-all $Default rule.
  • CI dry-run integration and explicitly gated deployment apply.

Remaining work

  • Extend the reconciler to provision and prune queues.
  • Add multi-topic/subscription and multi-queue subscriber configuration instead of the current single-source environment configuration.
  • Add production environment RBAC and managed-identity wiring for the reconciler.
  • Add an end-to-end test against an Azure Service Bus namespace.
  • Extend Logic Apps import to generate the native Azure Service Bus trigger contracts.
## Status update - 2026-08-18 The first Azure Service Bus implementation slice is now merged to `main`. ### Shipped - Topic publish. - Topic subscription peek-lock receive, complete, abandon, and dead-letter. - Queue send and receive. - Queue peek-lock complete, abandon, and dead-letter. - Topic subscription triggers with subscriber-owned settlement. - Queue triggers with subscriber-owned settlement. - Dashboard trigger picker entries for: - Azure Service Bus Topic subscription - Azure Service Bus Queue - Trigger-owned source configuration: - `servicebus.topic` + `servicebus.subscription` - `servicebus.queue` - Declarative Service Bus entity validation. - Dry-run-first reconciliation for enabled topic subscriptions. - DSAV SQL rule derivation and removal of the catch-all `$Default` rule. - CI dry-run integration and explicitly gated deployment apply. ### Remaining work - Extend the reconciler to provision and prune queues. - Add multi-topic/subscription and multi-queue subscriber configuration instead of the current single-source environment configuration. - Add production environment RBAC and managed-identity wiring for the reconciler. - Add an end-to-end test against an Azure Service Bus namespace. - Extend Logic Apps import to generate the native Azure Service Bus trigger contracts.
Author
Owner

Triage 2026-08-31

  • Prio: P2 (was P1 voor topics; native topics/queues/triggers zijn gemerged)
  • Status: leftover, ticket blijft open
  • Connector zelf is geen greenfield meer. Rest is platform-hardening.

Volgende slice (kies er een): queue-provisioning in de reconciler, of multi-source subscriber-config in plaats van single-source env. E2E tegen een echte namespace en Logic Apps-import mapping blijven later.

**Triage 2026-08-31** - **Prio:** P2 (was P1 voor topics; native topics/queues/triggers zijn gemerged) - **Status:** leftover, ticket blijft open - Connector zelf is geen greenfield meer. Rest is platform-hardening. **Volgende slice (kies er een):** queue-provisioning in de reconciler, of multi-source subscriber-config in plaats van single-source env. E2E tegen een echte namespace en Logic Apps-import mapping blijven later.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MeshFlowsGPL/meshflows#127
No description provided.