Skip to content

Blob Storage: Be able to set api version to use like in the Python package #31606

Open

Description

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I can't figure out how to set the outbound api version to use for BlobServiceClient in '@azure/storage-blob'. I would assume there might be two locations where we can set it but I don't see any options in the interfaces/types.

Best pratices in the API docs state that we should set the version, https://learn.microsoft.com/en-us/rest/api/storageservices/versioning-best-practices. While we don't have a use case to set the version on our prod/dev environments, this is breaking our testing.

Describe the solution you'd like

  • Instantiate the BlobServiceClient with an option to set API version, like how its done in https://learn.microsoft.com/en-us/python/api/azure-storage-blob/azure.storage.blob.blobserviceclient?view=azure-python#keyword-only-parameters

OR

  • Ability to set the API version in each outbound call site, such as createContainer

USE CASE
We are currently using test containers to spin up azurite instances. Since test containers use docker, we typically retrieve the latest image in our local cache. This means that if the node package updates and has a newer api version that a historical 'latest' image might not support, our testing environment breaks. We get the error of The API version 2024-11-04 is not supported by Azurite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Service AttentionWorkflow: This issue is responsible by Azure service team.StorageStorage Service (Queues, Blobs, Files)customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions