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

fix(az key vault): Raise an error instead of panic if authentication not provided #4017

Merged
merged 1 commit into from
Dec 15, 2022

Conversation

JorTurFer
Copy link
Member

Signed-off-by: Jorge Turrado jorge_turrado@hotmail.es

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #4010

…not provided

Signed-off-by: Jorge Turrado <jorge_turrado@hotmail.es>
@JorTurFer JorTurFer requested a review from a team as a code owner December 15, 2022 20:01
@zroubalik
Copy link
Member

Is there any e2e test using azure vault?

@JorTurFer
Copy link
Member Author

Yes, with both cases, using client credentials and also using podIdentity

@JorTurFer
Copy link
Member Author

JorTurFer commented Dec 15, 2022

/run-e2e vault*
Update: You can check the progress here

@JorTurFer JorTurFer merged commit eddae01 into kedacore:main Dec 15, 2022
@JorTurFer JorTurFer deleted the fix-pod-identity-panic branch December 15, 2022 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TriggerAuthentication with Azure Key Vault and azure-workload causes Panic/crash after upgrade to 2.9.0
2 participants