Replies: 1 comment 1 reply
-
Somewhat tangentially related to this, but rather than having a fixed list of container names, if we were to use a To offer a hypothetical scenario - if I were to have my image data for all customers stored within a single azure storage account, but each customer's image data is stored in its own container, each with a unique name (i.e. a GUID value). The advantages of this approach would be that our customer data isn't interspersed with one another, and we can perform operations on a single customer's data (e.g. move, delete, etc) with relative ease. The issue with the current implementation is that the container names need to be specified at startup, and we could have tenant operations (CRUD) happening after launch. |
Beta Was this translation helpful? Give feedback.
-
Good day,
I was looking at using this library in conjunction with ImageSharp as we do a fair amount of image processing.
However, I noticed that both
AzureBlobStorageCacheOptions
andAzureBlobStorageImageProviderOptions
only allow for the specification of connection strings. Given that Microsoft now recommend using token-based authentication, it might be preferable to instead allow for using token credentials instead.At the same time, would it make sense to use an injected
BlobServiceClient
, rather than instantiatingBlobContainerClient
directly?Beta Was this translation helpful? Give feedback.
All reactions