3.805.0

🐞 Bug fixes

• (Resolves issue with External link encoded after saving)

3.804.0

🎯 Development

• remove blob by full path only (#22)

3.803.0

🎯 Development

• Add the ability to connect Azure blob storage with SAS (#20)

Description

• Add the ability to connect Azure blob storage with shared access signatures (SAS)
• Refactor getting absolute and relative URI

References

https://learn.microsoft.com/en-us/azure/storage/common/storage-configure-connection-string#configure-a-connection-string-for-an-azure-storage-account
https://learn.microsoft.com/en-us/rest/api/storageservices/create-account-sas

3.802.0

🎯 Development

Two new events, BlobCreatedEvent and BlobDeletedEvent, have been added to enhance event-driven functionality within the system.

🔥 Breaking Changes

AzureBlobProvider constructor changed. The constructor signature for AzureBlobProvider has been modified to AzureBlobProvider(IOptions options, IFileExtensionService fileExtensionService, IEventPublisher eventPublisher) to address the VC0008 warning.

🎬 Action Required:
To resolve this breaking change, it is necessary to update the VirtoCommerce.FileSystemAssets to 3.801 and VirtoCommerce.Content to 3.801.

3.801.0

🎯 Development

• Allow creating non-public containers (#19)

Added new setting AllowBlobPublicAccess. Default value is true.

appsettings.json:

{
  "Assets": {
    "AzureBlobStorage": {
      "AllowBlobPublicAccess": true
    }
  },
  "Content": {
    "AzureBlobStorage": {
      "AllowBlobPublicAccess": true
    }
  }
}

3.800.1

🎯 Development

• Allow creating non-public containers (#19)

3.211.1

🎯 Development

• Allow creating non-public containers (#19)

3.800.0

🎯 Development

• (Update to .NET 8)
• change variable name (#17)

3.211.0

🐞 Bug fixes

• Fix breaking changes in 3.210

3.210.0

🔥 Breaking change

• RootPath settings is required for Assets/AzureBlobStorage; otherwise you will get error: System.ArgumentNullException: Value cannot be null.\r\n at VirtoCommerce.Platform.Core.Common.StringExtensions.IsAbsoluteUrl(String URL); We are working under the fix and planning to fix it in the next release.