-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Storage to azure-core preview 3 #4482
Conversation
* SAS implementation * Fixed some minor formatting issues * Fixed checkstyle problems and test issue
Removes RawClients from Storage Blobs
…to ContainerClient (Azure#4376) * Removed raw clients * Added deleteContainer to StorageClient * Added getAppendBlob with snapshot to ContainerClient
Closing in favor of #4489 |
* Initial check in for storage queue
…-for-java into storage-swagger
* Finished the restructure, refactor builder. Added sleep in record feature. Linting
…-for-java into storage-swagger
Merges AppendBlobClientBuilder, BlobClientBuilder, BlockBlobClientBuilder, and PageBlobClientBuilder into a single builder class BlobClientBuilder. Additionally, JavaDoc comments for the other builder classes, ContainerClientBuilder and StorageAccountClientBuilder, were cleaned up and the way the endpoint is handled in builders was changed.
…-for-java into storage-swagger
"required": true, | ||
"type": "string", | ||
"x-ms-parameter-location": "method", | ||
"x-ms-skip-url-encoding": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
James will discuss with team
@@ -3219,8 +3382,10 @@ | |||
"format": "etag" | |||
}, | |||
"Quota": { | |||
"type": "integer", | |||
"format": "int64", | |||
"type": "integer" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
James to discuss with team
@@ -98,7 +98,7 @@ | |||
public BlockBlobAsyncClient asBlockBlobAsyncClient() { | |||
return new BlockBlobAsyncClient(new AzureBlobStorageBuilder() | |||
.url(getBlobUrl().toString()) | |||
.pipeline(azureBlobStorage.httpPipeline()), snapshot); | |||
.pipeline(azureBlobStorage.getHttpPipeline()), snapshot); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jianghao to start discussion with James and Jonathan
https://github.com/azure/azure-sdk-for-java/issues/4556 --> | ||
<Match> | ||
<Or> | ||
<Class name="com.azure.security.keyvault.keys.KeyClient"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how was this spotbug issue resolved?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was brought in from merge - will revert.
…-java into storage-swagger
@@ -21,14 +21,14 @@ | |||
* <p>Create a pipeline without configuration</p> | |||
* | |||
* <pre> | |||
* HttpPipeline.builder() | |||
* new HttpPipelineBuilder() | |||
* .build(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Move the .build()
onto the same line.
if (snapshot != null) { | ||
urlBuilder.query("snapshot=" + snapshot); | ||
} | ||
return urlBuilder.toURL(); | ||
} catch (MalformedURLException e) { | ||
throw new RuntimeException(String.format("Invalid URL on %s: %s" + getClass().getSimpleName(), azureBlobStorage.url()), e); | ||
throw new RuntimeException(String.format("Invalid URL on %s: %s" + getClass().getSimpleName(), azureBlobStorage.getUrl()), e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI: This will very shortly result in CheckStyle check failure, as the clientLogger.logAndThrow
API should be used instead. The PR for this is soon to be merged here: #4566
We discussed this in our storage sync today and this can be merged now with follow up issues opened for the two follow ups:
|
No description provided.