mik-laj opened a new pull request #17011:
URL: https://github.com/apache/airflow/pull/17011


   The 1.10 series reached end of life, so the Dockerfile on main can drop 
support it.
   
   Additionally, this solves one problem that the user reported. We used CLI 
check for Airflow 1.10 to check the database connection, and for Airflow 2.0 
legacy check, which only supports some database engines.  However, we should do 
it the other way around. For Airflow 2.0, we should use a CLI check. 
   
   If we use CLI Check, we have MSSQL and any other backend support 
automatically.
   
   For details, see: https://github.com/apache/airflow/pull/16857
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to