-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
community: undo azure_ad_access_token breaking change #25818
community: undo azure_ad_access_token breaking change #25818
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
This fix is very important Pipeline broke, while nothing changed. Please merge this. For people googling this problem: |
I can create another PR for this, but the issue is
so defaulting it to None, means the order of parameters must change as parameters with default values must be after required paramers, and if the key is required, then the access token is not, and viceversa. @efriis @baskaryan what do you suggest here? |
not sure i follow, you're saying only one of azure_search_key and azure_ad_access_token is required? in that case we can update azure_search_key to be Optional[str]. But yea we can't give it a default value bc we'd need to move it then and that's a breaking change |
Well you authenticate with api key or with access token not with both, so that means both need to be optional with default to None? |
I checked master, it was fixed by adding None and changing the order, the PR was not reverted. |
No description provided.