Skip to content
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

Consider depending on azure-keyvault-secrets instead of azure-keyvault metapackage #22551

Closed
2 tasks done
xylar opened this issue Mar 27, 2022 · 1 comment · Fixed by #22557
Closed
2 tasks done

Consider depending on azure-keyvault-secrets instead of azure-keyvault metapackage #22551

xylar opened this issue Mar 27, 2022 · 1 comment · Fixed by #22557
Assignees
Labels
kind:feature Feature Requests

Comments

@xylar
Copy link
Contributor

xylar commented Mar 27, 2022

Description

It appears that the microsoft-azure provider only depends on azure-keyvault-secrets:

from azure.keyvault.secrets import SecretClient

and not the other 2 packages in the azure-keyvault metapackage.

Use case/motivation

I am the maintainer of the apache-airflow-providers-* packages on conda-forge and I'm running into small issues with the way azure-keyvault is maintained as a metapackage on conda-forge. I think depending on azure-keyvault-secrets explicitly would solve my problem and also provide better clarity for the microsoft-azure provider in general.

Related issues

conda-forge/azure-keyvault-feedstock#6
conda-forge/apache-airflow-providers-microsoft-azure-feedstock#13

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@xylar xylar added the kind:feature Feature Requests label Mar 27, 2022
@mik-laj
Copy link
Member

mik-laj commented Mar 27, 2022

@xylar Assigned!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature Feature Requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants