potiuk commented on issue #16254: URL: https://github.com/apache/airflow/issues/16254#issuecomment-856245357
OK. I see the problem @cvsekhar . It seems that the AzureFileServerHook was wrongly defined and the way extras were used there was wrong. Passing extras this way is not how airlfow works with connection extras - all extras are always prefixed with `extra__conn__` and your extras (and they way how the FileServerHook works). The AzureFileServerHook has been missing in the change and it does not rally work the same way - on one hand you have no dedicated hook, and on the other hand - the other "Azure" related hooks have some extras defined which are not properly configured. There are few ways you can mitigate the problem: 1) downgrade apache-airflow-providers-microsoft-azure to 1.3.0 - that is the most "certain" fix for you I think. 2) You can try to use the "Azure" connection instead in 2.0.0. Though it will likely fail with "extra__azure__tenantId" missing - looking at the code. 3) As a quick workaround, you should be able to use any "generic" connection. For example you can use HTTP connection and fill in the extras the way you used it. It **should** work just fine (though it is an abuse of how Airlfow connections work). This is probably the "fastest" workaround if it works for you Let me know if those work. In the meantime I might implement a quick fix - I am just about to release a new version of all providers but I think I can quickly fix this one in that upcoming version. I will ask you to test the RC version then OK ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
