Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Resolve key vault secret in parallel#192

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
zhiyuanliang-ms merged 5 commits intomainfromzhiyuanliang/secret-performance
May 14, 2025

Conversation

@zhiyuanliang-ms
Copy link
Member

@zhiyuanliang-mszhiyuanliang-ms commentedMay 7, 2025
edited
Loading

Why this PR?

#191

This change can bring about 40% speed-up when loading 10+ secrets.

Visible change

AddedKeyVaultOptions.parallelSecretResolutionEnabled option to allow resolving key vault secret in parallel.

Usage:

constcredential=newDefaultAzureCredential();constappConfig=awaitload("endpoint",credential,{keyVaultOptions:{credential:credential,parallelSecretResolutionEnabled:true}});

About Key Vault throttling

Key Vault allows 4000 transactions in 10 seconds, per vault per region.ref

  1. Key Vault SDK cannot be used in browser because of CORS. I have verified this. So, for the potential browser scenario of JS provider, people should not use Key Vault reference there. This significantly reduces the chance of Key Vault throttling as Key Vault reference is only valid to use in server scenario.

  2. For potential throttling response from Key Vault, thebest practice is to use the built-in retry policy configured through SecretClientOptions.

The provider supports either registeringSecretClient instances or configuringSecretClientOptions.ref

About cache for Key Vault secret

Secret cache is added in#175

@zhiyuanliang-mszhiyuanliang-ms marked this pull request as ready for reviewMay 13, 2025 07:40
@zhiyuanliang-mszhiyuanliang-ms merged commit986e3f0 intomainMay 14, 2025
6 checks passed
@zhiyuanliang-mszhiyuanliang-ms deleted the zhiyuanliang/secret-performance branchMay 14, 2025 03:15
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@juniwangjuniwangjuniwang left review comments

@CsCherrYYCsCherrYYCsCherrYY approved these changes

@drago-draganovdrago-draganovAwaiting requested review from drago-draganov

@zhenlanzhenlanAwaiting requested review from zhenlan

@jimmyca15jimmyca15Awaiting requested review from jimmyca15

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@zhiyuanliang-ms@juniwang@drago-draganov@jimmyca15@CsCherrYY

[8]ページ先頭

©2009-2025 Movatter.jp