-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[FEATURE REQ][Key Vault JCA] QoL changes for HttpUtil. #40956
Copy link
Copy link
Open
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.azure-springAll azure-spring related issuesAll azure-spring related issuesazure-spring-jcafeature-requestThis issue requires a new behavior in the product in order be resolved.This issue requires a new behavior in the product in order be resolved.
Milestone
Metadata
Metadata
Assignees
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.azure-springAll azure-spring related issuesAll azure-spring related issuesazure-spring-jcafeature-requestThis issue requires a new behavior in the product in order be resolved.This issue requires a new behavior in the product in order be resolved.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Todo
Just as outlined by #23547, the Key Vault JCA library is not up to par with other similar data plane libraries in our Azure SDK for Java. As part of the effort to align the library with the rest, we also need to add QoL changes to the
HttpUtilclass such as:HttpClientevery time an HTTP request needs to be made and instead use a longer-lived instance wherever possible.nullin methods such asget()orpost()when there's an error in sending a request/ receiving a response and instead bubble up a proper exception.RetryPolicy.