Skip to content

Key Vault clients use azure-identity credentials #5694

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

Merged
merged 16 commits into from
Jun 8, 2019

Conversation

chlowell
Copy link
Member

@chlowell chlowell commented Jun 5, 2019

This closes #5551 and resolves #4877 by refactoring clients to share a common __init__ which accepts azure-identity credentials, builds a pipeline including the token auth policy from azure-core, and allows specifying a Key Vault API version. The a/sync inits could be combined; I kept them separate in case we decide to spin off async packages.

I also refactored VaultClientPreparer to use azure-identity's environment credentials in live tests, and added a preparer and test case class for async tests.

There are a few small miscellaneous fixes here as well, including one that closes #5604.

Work remains on the tests. The live tests are unreliable. Making them reliable requires larger changes I don't want to cram into this PR (tracked by #5693). Also, I replaced ServicePrincipalCredentials in examples with azure-identity's ClientSecretCredential, but examples should show the default credential instead. That doesn't exist yet, so it's also work for a future PR (tracked by #5006).

@chlowell chlowell added KeyVault Client This issue points to a problem in the data-plane of the library. labels Jun 5, 2019
@chlowell chlowell requested a review from samvaity June 5, 2019 16:46
@chlowell chlowell requested a review from schaabs as a code owner June 5, 2019 16:46
@chlowell chlowell self-assigned this Jun 5, 2019
@adxsdk6
Copy link

adxsdk6 commented Jun 5, 2019

Can one of the admins verify this patch?

Copy link
Contributor

@schaabs schaabs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@chlowell chlowell force-pushed the keyvault-identity branch from 5d5338e to 94d2390 Compare June 7, 2019 21:46
@chlowell chlowell force-pushed the keyvault-identity branch from d256621 to 3a9dc8a Compare June 7, 2019 22:54
@chlowell chlowell merged commit ee8ff2c into Azure:master Jun 8, 2019
@chlowell chlowell deleted the keyvault-identity branch June 8, 2019 00:18
rajivnandivada pushed a commit to rajivnandivada/azure-sdk-for-python that referenced this pull request Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault
Projects
None yet
3 participants