-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Problem with Microsoft Azure Provider base_azure hook #33025
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
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
@shakeelansari63 This looks like a simple change but I have not been able to replicate this with the code you provided. Can you review this or do you have an example DAG that can illustrate the problem? |
Hi @nathadfield , Here is example - Note: I haven't added any key_json or key_path in extra. Which means, following piece of code will be ran to instanciate the client - And When I call the get_conn() method, it gives following error - And this error is because it need |
@shakeelansari63 Having made this change, we are now encountering test failures and so I remain unconvinced that this is indeed a problem.
|
Changing this seems to break |
I added a comment on the PR guessing that could be the cause for failing tests #33040 (comment) |
@nathadfield , I got the issue here. I looked into one of the failure, for ContainerInstanceManagementClient. This is from
This is very old version of azure SDK (from 2019) which is still using |
From what I can see from Pypi, latest version of |
@shakeelansari63 Yep. I'll ask around to see what I can find out but it seems like you won't be able to use |
I'm closing this issue as the root cause is updating old package as listed in #30199 PRs are welcome. |
While working on issue apache#33025, it was unclear on why we've pinned dependencies for Azure integration. And it was pointed out that we have an open issue for this. Link the same along with the TODO in the provider.yaml so that if someone takes a look later, they will know that we have an issue for it and the issue has relevant description.
…3064) While working on issue #33025, it was unclear on why we've pinned dependencies for Azure integration. And it was pointed out that we have an open issue for this. Link the same along with the TODO in the provider.yaml so that if someone takes a look later, they will know that we have an issue for it and the issue has relevant description.
…3064) While working on issue apache/airflow#33025, it was unclear on why we've pinned dependencies for Azure integration. And it was pointed out that we have an open issue for this. Link the same along with the TODO in the provider.yaml so that if someone takes a look later, they will know that we have an issue for it and the issue has relevant description. GitOrigin-RevId: a069965df84273c65e23d1fda9ffa47a58ed6732
…3064) While working on issue apache/airflow#33025, it was unclear on why we've pinned dependencies for Azure integration. And it was pointed out that we have an open issue for this. Link the same along with the TODO in the provider.yaml so that if someone takes a look later, they will know that we have an issue for it and the issue has relevant description. GitOrigin-RevId: a069965df84273c65e23d1fda9ffa47a58ed6732
…3064) While working on issue apache/airflow#33025, it was unclear on why we've pinned dependencies for Azure integration. And it was pointed out that we have an open issue for this. Link the same along with the TODO in the provider.yaml so that if someone takes a look later, they will know that we have an issue for it and the issue has relevant description. GitOrigin-RevId: a069965df84273c65e23d1fda9ffa47a58ed6732
…3064) While working on issue apache/airflow#33025, it was unclear on why we've pinned dependencies for Azure integration. And it was pointed out that we have an open issue for this. Link the same along with the TODO in the provider.yaml so that if someone takes a look later, they will know that we have an issue for it and the issue has relevant description. GitOrigin-RevId: a069965df84273c65e23d1fda9ffa47a58ed6732
…3064) While working on issue apache/airflow#33025, it was unclear on why we've pinned dependencies for Azure integration. And it was pointed out that we have an open issue for this. Link the same along with the TODO in the provider.yaml so that if someone takes a look later, they will know that we have an issue for it and the issue has relevant description. GitOrigin-RevId: a069965df84273c65e23d1fda9ffa47a58ed6732
Uh oh!
There was an error while loading. Please reload this page.
Apache Airflow version
2.6.3
What happened
When using AzureBaseHook from airflow/providers/microsoft/azure/hooks/base_azure.py with SDKClient class, the get_conn() method fails to instanciate the Client class object.
The error message says,
missing parameter credential
This is because the sdk_client is being instanciated with
credentials=ServicePrincipalCredentials
Notice an extra
s
in credentials key which is not needed.What you think should happen instead
The sdk_client should be instanciated with
credential=ServicePrincipalCredential
which will be instanciated correctlyHow to reproduce
Install any Azure client, let's say azure-monitor-query
pip install azure-monitor-query
Use the Azure connection with Azure client
This will fail -
Operating System
Any
Versions of Apache Airflow Providers
apache-airflo-providers-microsoft-azure v6.2.1
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: