Add Secrets backend for Microsoft Azure Key Vault #10898
Conversation
boring-cyborg
bot
added
area:docs
area:secrets
provider:microsoft-azure
|
k8s failures are unrelated |
Need rebase - that was one of the previous master merges (fixed afterwards) I had the same problem with two other prs and it was fixed after rebase |
Co-authored-by: Elwin Arens <[email protected]>
kaxil
force-pushed
the
azure-serets-manager
branch
from
6b06535
to
e8d7226
Compare
rebased |
|
I think we have a failing pylint in master now because of this one :( |
|
@kaxil ^^ |
|
Checking |
|
No, I think the test was cancelled because another PR was merged, I can't see any error |
|
In another PR |
|
I am running my PR rebased on master now https://github.com/apache/airflow/pull/10912/checks?check_run_id=1108699419 |
|
Hmm. It works. It was an interesting race condition that I must have to take a closer look at :) |
|
Allright I know @kaxil . It was manifestation of the #10471 Currenlty the image is built using the original commit, but the build itself is run using sources after the PR is automatically merged with master. So in the image there was no "azure-identity" and the other package added, but the sources used for pylint check already contained it (because we run static checks using the local sources). That makes me think that I might want to try to solve it eventually. |
(cherry picked from commit f77a11d)
(cherry picked from commit f77a11d)
(cherry picked from commit f77a11d)
(cherry picked from commit f77a11d)
|
Thanks for the effort of picking up where i left, everyone! |
(cherry picked from commit f77a11d)
(cherry picked from commit f77a11d)
(cherry picked from commit f77a11d)
(cherry picked from commit f77a11d)
Co-authored-by: Elwin Arens [email protected]
closes: #8258
This PR adds secrets backend for Microsoft azure key vault
This work was started at #9639
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.