Status of testing Providers that were prepared on December 07, 2021

[potiuk]

Body

I have a kind request for all the contributors to the latest provider packages release.
Could you help us to test the RC versions of the providers and let us know in the comment,
if the issue is addressed there.

Providers that need testing

Those are providers that require testing as there were some substantial changes introduced:

Provider databricks: 2.1.0rc2

• Databricks: add more methods to represent run state information (#19723): @alexott
• Databricks - allow Azure SP authentication on other Azure clouds (#19722): @alexott
• Databricks: allow to specify PAT in Password field (#19585): @alexott
• Databricks jobs 2.1 (#19544): @christophergrant
• Update Databricks API from 2.0 to 2.1 (#19412): @Mokubyow
• Authentication with AAD tokens in Databricks provider (#19335): @alexott
• Fixup string concatenations (#19099): @blag
• Databricks hook: fix expiration time check (#20036): @alexott

Committer

• I acknowledge that I am a maintainer/committer of the Apache Airflow project.

[alexott]

Tested #19585, #19335, #19443, #19544 - looks good

P.S. #19443 is missing from the changelog

[potiuk]

P.S. #19443 is missing from the changelog

Ah yeah. Good point - I have mistakenly hidden it in the changelog - it is in the hidden section among refactoring (my bad) - see here - it is under "Below changes are excluded from the changelog":

https://raw.githubusercontent.com/apache/airflow/main/airflow/providers/databricks/CHANGELOG.rst

I will restore it in the documentation in https://airflow.apache.org/docs/apache-airflow-providers-databricks/stable/index.html - before publishing the docs (I can do it) - but I won't add it back (yet) in the PyPI package README (I can't - it's part of the package). But I will correct it in the CHANGELOG and when we release the next version (I see there are already some changes in progress :) it will appear back in the PyPI changelog when we release December wave.

[alexott]

Thank you Jarek

[kaxil]

-1 for Databricks provider. The change in #19835 causes DB call in init (which was fixed in last version). @josh-fell will have a PR in a bit to fix it

[potiuk]

Cancelling it then

[josh-fell]

#20180 has now been merged to remove the db call.