Deprecated API
Contents
-
ClassDescriptionConsider configuring timeouts with
HttpClientOptions
.Should not use this class outside of azure-security-keyvault-jca.jar. Move this class to implementation package.UseProgressReporter
Please use the generateSas method on the desired blob/container client after initializingBlobServiceSasSignatureValues
.UseProgressReporter
Please use the generateSas method on the desired service client after initializingAccountSasSignatureValues
.Please use the generateSas method on the desired client after initializing the appropriate SasSignatureValues object.Please use the generateSas method on the desired file/share client after initializingShareServiceSasSignatureValues
.Please use the generateSas method on the desired queue client after initializingQueueServiceSasSignatureValues
.
-
EnumDescriptionThe version is set to the latest version of sas.
-
Annotation TypeDescriptionThis interface is no longer used, or respected, in code.
-
FieldDescriptionDeprecated in favor of PARENT_TRACE_CONTEXT_KEY, use it to propagate full io.opentelemetry.ContextAs of 4.1.0, replaced by
SystemEventNames.COMMUNICATION_CHAT_PARTICIPANT_REMOVED_FROM_THREAD
.
-
MethodDescriptionUse synchronous token refresher instead.Use
HttpHeaders.set(String, String)
instead.deprecated in favor ofNettyAsyncHttpClientBuilder.eventLoopGroup(EventLoopGroup)
.UseClientOptions
to configureapplicationId
.UseClientOptions
to configureapplicationId
.refer the decoration samples forPagedFlux.create(Supplier)
.This method is deprecated as JUnit 5 provides a simpler mechanism to get the test method name throughTestInfo
. Keeping this for backward compatability of other client libraries that still override this method. This method can be deleted when all client libraries remove this method. SeeTestBase.setupTest(TestInfo)
.UseConfigurationBuilder
andConfigurationSource
to create configuration.UseConfigurationBuilder
andConfigurationSource
to provide all properties before creating configuration.UseConfigurationBuilder
andConfigurationSource
to provide all properties before creating configuration.Use localized implementation.UseClientLogger.logThrowableAsWarning(Throwable)
instead.deprecated to avoid directObjectMapper
usage in favor of using more resilient and debuggableJacksonAdapter
APIs.deprecated, useJacksonAdapter(BiConsumer<ObjectMapper, ObjectMapper>)
constructor to configure modules.Configure the proxy options on theHttpClient
instead and then set that client on the credential usingCredentialBuilderBase.httpClient(HttpClient)
.Configure the redirect URL ashttp://localhost:{port}
viaInteractiveBrowserCredentialBuilder.redirectUrl(String)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionCancelEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionCancelEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionCancelEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionCancelEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionCancelEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionCancelEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionFailureEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionFailureEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionFailureEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionFailureEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionFailureEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionFailureEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionSuccessEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionSuccessEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionSuccessEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceActionSuccessEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionSuccessEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceActionSuccessEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteCancelEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteCancelEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteCancelEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteCancelEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteCancelEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteCancelEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteFailureEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteFailureEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteFailureEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteFailureEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteFailureEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteFailureEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteSuccessEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteSuccessEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteSuccessEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteSuccessEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteSuccessEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceDeleteSuccessEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteCancelEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteCancelEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteCancelEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteCancelEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteCancelEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteCancelEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteFailureEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteFailureEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteFailureEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteFailureEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteFailureEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteFailureEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteSuccessEventData.getResourceAuthorization()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteSuccessEventData.getResourceClaims()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteSuccessEventData.getResourceHttpRequest()
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteSuccessEventData.setResourceAuthorization(ResourceAuthorization)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteSuccessEventData.setResourceClaims(Map)
instead.This method is no longer supported since v4.9.0.Use
ResourceWriteSuccessEventData.setResourceHttpRequest(ResourceHttpRequest)
instead.Replaced byEventHubClientBuilder.retryOptions(AmqpRetryOptions)
.UseOcrSkill.isShouldDetectOrientation()
instead.use withLimit insteaddue to refactoring code to be in the common storage library.Please useBlobUrlParts.getCommonSasQueryParameters()
BlobContainerListDetails
now contains multiple options. This will only convert result of {BlobContainerListDetails.setRetrieveMetadata(boolean)
} for backwards compatibility.useBlobParallelUploadOptions.getOptionalLength()
to have safe access to a length that will not always exist.UseBlobClient.uploadWithResponse(BlobParallelUploadOptions, Duration, Context)
to specify timeout.UseBlobClient.uploadWithResponse(BlobParallelUploadOptions, Duration, Context)
to specify timeout.Destination container name must match deleted container nameDestination container name must match deleted container nameUseProgressReporter
instead.UseProgressReporter
instead.Please use the generateSas method on the desired blob/container client after initializingBlobServiceSasSignatureValues
.Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues
Please use the generateUserDelegationSas(BlobServiceSasSignatureValues, UserDelegationKey) method on the desired container/blob client after initializingBlobServiceSasSignatureValues
.Please use the generateSas(BlobServiceSasSignatureValues) method on the desired container/blob client after initializingBlobServiceSasSignatureValues
.Blob name is now auto-populated by the SAS generation methods provided on the desired blob client.Container name is now auto-populated by the SAS generation methods provided on the desired container/blob client.Snapshot id is now auto-populated by the SAS generation methods provided on the desired (snapshot) blob client.Please use the SAS generation methods provided on the desired blob client that will auto-populate the blob name.Please use the SAS generation methods provided on the desired container/blob client that will auto-populate the container name.Please use the SAS generation methods provided on the desired (snapshot) blob client that will auto-populate the snapshot id.The version is set to the latest version of sas. Users should stop calling this API as it is now treated as a no-op.useBlobAsyncClientBase.downloadStream()
instead.useBlobClientBase.downloadStream(OutputStream)
instead.Please useRequestRetryOptions.getTryTimeoutDuration()
Please useRequestRetryOptions.getTryTimeoutDuration()
Please useRequestRetryOptions.getTryTimeoutDuration()
UseProgressReporter
UseProgressReporter
Please use the generateSas method on the desired service client after initializingAccountSasSignatureValues
.Please useAccountSasSignatureValues
Please useAccountSasSignatureValues
Please use the generateAccountSas(AccountSasSignatureValues) method on the desired service client after initializingAccountSasSignatureValues
.Please useAccountSasSignatureValues(OffsetDateTime, AccountSasPermission, AccountSasService, AccountSasResourceType)
to specify the expiry time.Please useAccountSasSignatureValues(OffsetDateTime, AccountSasPermission, AccountSasService, AccountSasResourceType)
to specify the allowed permissions.Please useAccountSasSignatureValues(OffsetDateTime, AccountSasPermission, AccountSasService, AccountSasResourceType)
to specify the resource types being targeted.Please useAccountSasSignatureValues(OffsetDateTime, AccountSasPermission, AccountSasService, AccountSasResourceType)
to specify the services being targeted.The version is set to the latest version of sas. Users should stop calling this API as it is now treated as a no-op.Please use the generateSas method on the desired client after initializing the appropriate SasSignatureValues object.Please use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesPlease use SasSignatureValuesUseStorageImplUtils.parseDateAndFormat(String)
useFileParallelUploadOptions.getOptionalLength()
to have safe access to a length that will not always exist.Destination file system name must match deleted file system nameDestination file system name must match deleted file system nameThe version is set to the latest version of sas. Users should stop calling this API as it is now treated as a no-op.Please useShareProperties.setProvisionedBandwidthMiBps(Integer)
()}Please useShareProperties.setProvisionedBandwidthMiBps(Integer)
()}Please use the generateSas method on the desired file/share client after initializingShareServiceSasSignatureValues
.Please useShareServiceSasSignatureValues
Please useShareServiceSasSignatureValues
Please useShareServiceSasSignatureValues
Please useShareServiceSasSignatureValues
Please useShareServiceSasSignatureValues
Please useShareServiceSasSignatureValues
Please useShareServiceSasSignatureValues
Please use the generateSas(ShareServiceSasSignatureValues) method on the desired share/file/directory client after initializingShareServiceSasSignatureValues
.File path is now auto-populated by the SAS generation methods provided on the desired file/directory client.Share name is now auto-populated by the SAS generation methods provided on the desired share/file/directory client.Please use the generateSas methods provided on the desired file/directory client that will auto-populate the file path.Please use the generateSas methods provided on the desired share/file/directory client that will auto-populate the share name.The version is set to the latest version of sas. Users should stop calling this API as it is now treated as a no-op.UseShareFileAsyncClient.uploadRange(Flux, long)
instead. Or considerShareFileAsyncClient.upload(Flux, ParallelTransferOptions)
for an upload that can handle large amounts of data.UseShareFileAsyncClient.uploadRangeWithResponse(ShareFileUploadRangeOptions)
instead. Or considerShareFileAsyncClient.uploadWithResponse(ShareFileUploadOptions)
for an upload that can handle large amounts of data.UseShareFileAsyncClient.uploadRangeWithResponse(ShareFileUploadRangeOptions)
instead. Or considerShareFileAsyncClient.uploadWithResponse(ShareFileUploadOptions)
for an upload that can handle large amounts of data.UseShareFileClient.uploadRange(InputStream, long)
instead. Or considerShareFileClient.upload(InputStream, long, ParallelTransferOptions)
for an upload that can handle large amounts of data.UseShareFileClient.uploadRangeWithResponse(ShareFileUploadRangeOptions, Duration, Context)
instead. Or considerShareFileClient.uploadWithResponse(ShareFileUploadOptions, Duration, Context)
for an upload that can handle large amounts of data.UseShareFileClient.uploadRangeWithResponse(ShareFileUploadRangeOptions, Duration, Context)
instead. Or considerShareFileClient.uploadWithResponse(ShareFileUploadOptions, Duration, Context)
for an upload that can handle large amounts of data.Please useShareLeaseAsyncClient.getResourceUrl()
Please useShareLeaseClient.getResourceUrl()
usePeekedMessageItem.getBody()
instead.usePeekedMessageItem.setBody(BinaryData)
instead.useQueueMessageItem.getBody()
instead.useQueueMessageItem.setBody(BinaryData)
instead.Please use the generateSas method on the desired queue client after initializingQueueServiceSasSignatureValues
.Please useQueueServiceSasSignatureValues
Please use the generateSas(QueueServiceSasSignatureValues) method on the desired queue client after initializingQueueServiceSasSignatureValues
.Queue name is now auto-populated by the SAS generation methods provided on the desired queue client.Please use the generateSas methods provided on the desired queue client that will auto-populate the queue name.The version is set to the latest version of sas. Users should stop calling this API as it is now treated as a no-op.
-
ConstructorDescriptionUse
CommunicationTokenRefreshOptions(Supplier)
instead and chain fluent setterCommunicationTokenRefreshOptions.setRefreshProactively(boolean)
UseInterceptorManager(TestContextManager)
instead.UseInterceptorManager(String, Map, boolean)
instead.UseInterceptorManager(String, Map, boolean, String)
instead.UseConfigurationBuilder
andConfigurationSource
that allow to provide all properties before creating configuration and keep it immutable.Use fluent interface to set properties instead.Use fluent interface to set properties instead.length is no longer necessary; useBlobParallelUploadOptions(InputStream)
instead.Please useBlobServiceSasSignatureValues
Please useBlobServiceSasSignatureValues(String)
,BlobServiceSasSignatureValues(OffsetDateTime, BlobSasPermission)
, orBlobServiceSasSignatureValues(OffsetDateTime, BlobContainerSasPermission)
followed by calls to the desired setters.Use fluent interface to set properties instead.Please use SasSignatureValuesPlease use SasSignatureValueslength is no longer necessary; useFileParallelUploadOptions(InputStream)
instead.length is no longer necessary; useShareFileUploadOptions(InputStream)
instead.Please useShareServiceSasSignatureValues
Please useQueueServiceSasSignatureValues
ProgressListener
.