We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
One specific example is that SecretClient constructs its own Uri for pageables and should use KeyVaultPipeline.CreateFirstPageUri like KeyClient.
SecretClient
Uri
KeyVaultPipeline.CreateFirstPageUri
KeyClient
The text was updated successfully, but these errors were encountered:
Pushing to November since this has no impact on the public APIs.
Sorry, something went wrong.
Use KeyVaultPipeline for SecretClient
5a0f002
Resolves Azure#8115
Resolve several Key Vault backlog issues (#25593)
71054d5
* Use operation helpers Partially fixes #22912 * Resolve PR feedback * Add OperationInternal tests * Use OperationInternal for all pseudo-LROs Resolves #22912 * Use KeyVaultPipeline for SecretClient Resolves #8115 * Deduplicate identifier parsing Resolves #24262 * Resolve PR feedback
heaths
Successfully merging a pull request may close this issue.
One specific example is that
SecretClient
constructs its ownUri
for pageables and should useKeyVaultPipeline.CreateFirstPageUri
likeKeyClient
.The text was updated successfully, but these errors were encountered: