Skip to content

Outbox blobs reach the worker over Event Grid - #7

Merged
fw2568 merged 2 commits into
mainfrom
feature/outbox-event-grid
Oct 25, 2026
Merged

fw2568 merged 2 commits into
mainfrom
feature/outbox-event-grid

Conversation

@fw2568

@fw2568 fw2568 commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

Attachments the cloud writes to bote-outbox reached clients only after a restart of the worker: blob extension 5.3.8 finds only blobs written before the host's first poll (Azure/azure-sdk-for-net#61660). 5.3.10 fixes it but needs Azure.Core 1.53 / System.Memory.Data 10.0.3, which the Functions host does not ship (host crashes, see #6).

  • Event Grid system topic on the gateway storage sends BlobCreated under bote-outbox/ to the queue bote-outbox-created; the new CloudOutboxBlobCreated queue trigger starts the copy, the same code as before.
  • The blob trigger stays for Azurite and is turned off in Azure with AzureWebJobs.CloudOutboxBlobDetected.Disabled (measured on Container Apps: the __ form leaves it polling).
  • OutboxEvents reads tenant and attachment from the event; tests use the event as Event Grid wrote it on staging.

…pies them to the clients from its queue

The blob trigger's polling scan misses blobs: extension 5.3.8 finds only those written before the
host's first poll (Azure/azure-sdk-for-net#61660), and 5.3.10, which fixes it, needs an Azure.Core
the Functions host does not ship. The blob trigger stays for storages without Event Grid (Azurite)
and is off in Azure.
@fw2568
fw2568 merged commit 3de8780 into main Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant