[ https://issues.apache.org/jira/browse/JCLOUDS-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211055#comment-17211055
]
Ignasi Barrera commented on JCLOUDS-1554:
-----------------------------------------
In the compute provider we had to deal with different versions depending on the API we were
using. VM API used a different version than Disk API, etc.
To provide more flexibility there without requiring to build a new context, we built a request
filter that read the version from the context properties:
* Filter: https://github.com/apache/jclouds/blob/master/providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/filters/ApiVersionFilter.java
* Default values:https://github.com/apache/jclouds/blob/master/providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/AzureComputeProviderMetadata.java#L112-L138
* Usage: https://github.com/apache/jclouds/blob/master/providers/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/features/AvailabilitySetApi.java#L51
I don't know if this applies here or it could be useful; it just came to my mind when reading
the issue :)
> Upgrade to Azure Blob API 2019-12-12
> ------------------------------------
>
> Key: JCLOUDS-1554
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1554
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-blobstore
> Affects Versions: 2.2.1
> Reporter: Andrew Gaul
> Assignee: Andrew Gaul
> Priority: Major
> Labels: azureblob
>
> This allows 5 GB single-part objects:
> https://docs.microsoft.com/en-us/rest/api/storageservices/versioning-for-the-azure-storage-services
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
|