add source to blob_trigger #196
Conversation
YunchuWang
requested review from
vrdmr,
gavin-aguiar and
pdthummar
as code owners
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #196 +/- ##
==========================================
+ Coverage 93.10% 93.11% +0.01%
==========================================
Files 56 56
Lines 3247 3253 +6
Branches 666 666
==========================================
+ Hits 3023 3029 +6
Misses 137 137
Partials 87 87
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #196 +/- ##
==========================================
+ Coverage 93.10% 93.11% +0.01%
==========================================
Files 56 56
Lines 3247 3253 +6
Branches 666 666
==========================================
+ Hits 3023 3029 +6
Misses 137 137
Partials 87 87
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Fixes #197
Context and Problem:
Issue #197 highlighted a discrepancy in the Azure Functions documentation and the actual behavior of the BlobTrigger binding. According to the documentation, the BlobTrigger binding supports a source argument that allows setting the source of the triggering event to EventGrid for lower latency. However, in practice, the BlobTrigger binding does not currently accept this argument, and the default method for detecting changes in a blob container is through the standard polling mechanism (LogsAndContainerScan).
Objective:
This Pull Request aims to align the functionality of the BlobTrigger with the documented features by introducing the EventGrid source option. This will enable users to leverage Event Grid-based triggers for blob storage, providing a more efficient and lower-latency mechanism for blob event handling.