-
Notifications
You must be signed in to change notification settings - Fork 488
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
Azure auth: do not use CLI provider by default when running in a cloud service #3338
Conversation
…d service This seems to be causing some issues for customers, and in a cloud service the CLI credentials would not work anyways. Signed-off-by: ItalyPaleAle <[email protected]>
Looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change IMO. Never mind
Please look at the diff. This only impacts when running in a cloud service. outside of a cloud service, CLI credentials still work |
/ok-to-test |
Components certification testCommit ref: 8fed634 ❌ Some certification tests failedThese tests failed:
|
Components conformance testCommit ref: 8fed634 ✅ All conformance tests passedAll tests have reported a successful status |
Complete Build MatrixThe build status is currently not updated here. Please visit the action run below directly. Commit ref: 8fed634 |
…d service (#3338) Signed-off-by: ItalyPaleAle <[email protected]>
This seems to be causing some issues for customers, and in a cloud service the CLI credentials would not work anyways.