potiuk opened a new pull request #16388:
URL: https://github.com/apache/airflow/pull/16388


   The Azure File Share connection has not been creted in #15159 and it
   caused an unexpected side effect as the default Azure Connection
   passed service_options dictionary to FileService
   with key that was unexpected.
   
   This change fixes two things:
   
   1) adds AzureFileShare connection that has separate conn_type
      and handles the extra_options specific for FileService Hook
      available in the Airflow UI.
   
   2) handles the "deprecated" way of passing keys without UI prefix
      but raises a deprecation warning when such key is passed or
      when the Wasb connection is used with an empty extras rather
      than Azure File Share.
   
   Fixes #16254
   
   <!--
   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.

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


Reply via email to