- Fixed a bug where polling for new blobs fails to detect newly created blobs when the List Blobs/Get Blobs operation requires multiple requests. If a blob is added or modified after LogScan begins, and is listed during the later portion of the listing, any blobs changed between the listing start time and the last modified timestamp of blobs found later will not be flagged as new in the subsequent LogScan.
- The following optimizations were added to Blob Trigger processing:
- Exclude containers that are not intended for monitoring.
- Do not perform unnecessary scanning for container(s) detected during the initial write log.
- Cache recently found write entry to avoid analyzing log blobs again.
- Migrate ScaleMonitor to TargetScaler.
- Reverted change where the scan will continue scanning AzureWebJobsStorage even when configuring a target storage account
- Fixed bug where the scan will continue scanning AzureWebJobsStorage even when configuring a target storage account
- This release contains bug fixes to improve quality.
- Upgraded
System.Text.Jsonpackage dependency to 6.0.10 for security fix.
- This release contains bug fixes to improve quality.
- Rely on PeekMessagesAsync when calculating message queue length
- Fixing target base scale instance concurrency for queues
- Bumped version of Azure.Storage.Blobs to resolve issue where Blob Path was being truncated at '#' character.
- Includes all features from 5.3.0-beta.1.
- Bumped Azure.Identity dependency to 1.11.1 to resolve security vulnerability.
- This release contains bug fixes to improve quality.
- This release contains bug fixes to improve quality.
- This release contains bug fixes to improve quality.
- Updating ParameterBindingData "Connection" value to the full connection name instead of the connection section key
- Added support for
BlobsOptions.PoisonBlobThreshold
- Loosen parameter binding data parsing and validation to allow binding BlobContainerClient without blob name. (#37124)
- Fixed bug where the blob container would scan from the beginning due not correctly updating the latest scan time. (#35145)
- Bumped Azure.Core dependency from 1.28 and 1.30, fixing issue with headers being non-resilient to double dispose of the request.
- Includes all features from 5.1.0-beta.1.
- Added Target Based Scaling support for Storage Queues and Blobs
- Added logging for details of a storage blob listener on start/stop operations.
- Updated BlobNameValidationAttribute to allow $web as a container name.
- Added Blob storage support for ParameterBindingData reference type.
- Implemented caching blobs in shared memory for faster I/O.
- General availability of Microsoft.Azure.WebJobs.Extensions.Storage.Blobs 5.0.0.
- Fixed bug where internal message format of blob trigger didn't interop with previous major versions of the extension.
- Adding Dynamic Concurrency support.
- Execution log when using Event Grid Blob Trigger vs Blob Trigger.
- Fix bug where dynamic SKU is not recognized correctly.
- This release contains bug fixes to improve quality.
- Added new configuration formats so extensions that need multiple storage services can specify them in one connection configuration.
Sample config:
{
"MyStorageConnection1": {
"blobServiceUri": "https://<my_account>.blob.core.windows.net",
"queueServiceUri": "https://<my_account>.queue.core.windows.net"
},
"MyStorageConnection2": {
"accountName": "<my_account>"
}
}- The configuration section name for URI configuration was changed from
endpointtoserviceUrito be consistent with other clients.
In case of JSON, from:
{
"MyConnection": {
"endpoint": "https://<my_account>.blob.core.windows.net"
}
}To
{
"MyConnection": {
"serviceUri": "https://<my_account>.blob.core.windows.net"
}
}Or using environment variables, from:
MyConnection__endpoint=https://<my_account>.blob.core.windows.net
To
MyConnection__serviceUri=https://<my_account>.blob.core.windows.net
- EventGrid support for the Blob Trigger was added. Details of the feature can be found here.
This is the first preview of the next generation of Microsoft.Azure.WebJobs.Extension.Storage which has been integrated with latest Azure Storage SDK that follows the Azure SDK Design Guidelines for .NET which provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more.
The Microsoft.Azure.WebJobs.Extension.Storage.Blobs offers drop-in replacement for scenarios where Blob and BlobTrigger attributes were bound to BCL types or user defined POCOs. Advanced scenarios like binding to Azure Storage Blobs SDK types or using BlobsOptions may require code changes.
This is a Public Preview version, so expect incompatible changes in subsequent releases as we improve the product. To provide feedback, please submit an issue in our Azure SDK for .NET GitHub repo.
- The extension has been split per storage service, i.e.
Microsoft.Azure.WebJobs.Extension.Storage.Blobshas been created. - The extension uses V12 Azure Storage SDK.
- Added support for token credential authentication using Azure.Identity library, including support for managed identity and client secret credentials.
- Simplified parallelism control through single
BlobsOptions.MaxDegreeOfParallelismproperty. - The
BlobsOptions.CentralizedPoisonQueuehas been removed. The implicit poison queue for aBlobTriggeris located in target blob's account by default.