Integration Error between azure-blob-storage container and Python Client about azure-sdk-for-python

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jalauzon-msft @vincenttran-msft.

[AlanTuring1988]

I tried with version 12.5.0 of the python sdk and the problem not exist. in fact I uploaded the blob locally and then check it on the cloud.

[swathipil]

Hi @AlanTuring1988 - thanks for opening an issue. We'll take a look asap!

[jalauzon-msft]

Hi @AlanTuring1988, the main reason for the behavior you are seeing is that that Docker image does not stay up to date with the Storage service in terms of API versions. In fact, it looks like it has not been updated in some time. That page says the last API version they added support for was 2020-04-08 which is quite old. I'm not sure if this image is deprecated or what is going on there. Perhaps they have added support for newer ones without specifying.

With each minor release of the SDK, we update the default API version that is used to the latest supported by the live Azure Storage service. For 12.19.1 that is 2023-11-03 which is what you are seeing in the error message. As mentioned, it seems that image may only support up to 2020-04-08.

So, you have two options:

• You can downgrade your SDK version, like you have done (I am not quite sure what is the latest version you can use as we did not used to write the API version in the CHANGELOG but it seems like it will have to be before 12.9.0 at least).
• You can try using the latest SDK but manually setting the API version in the client constructor using the api_version keyword. Anything in this list is valid but you may want to start with 2020-04-08 and work your way up.
  • There is a chance, depending on what operations and auth type you are using, that this does not work as changes in the SDK are not always backwards compatible with older API versions.

You can also try submitting feedback for that image here to see if there are plans to update it further or whether there is a replacement. (The SDK team is not familiar with it at all.)

[github-actions]

Hi @AlanTuring1988. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.