andyguwc opened a new pull request, #37922:
URL: https://github.com/apache/airflow/pull/37922

   This PR updates SnowflakeSqlApiHook to support 
[OAuth](https://docs.snowflake.com/en/developer-guide/sql-api/authenticating#using-oauth).
   
   In order to update this hook have to update the `SnowflakeHook` to parse the 
refresh token and client credentials.
   
   The OAuth workflow assumes the user already obtained the `refresh_token`, 
`client_id`, and `client_secret`. In particular the `refresh_token` should be 
obtained outside of airflow. 
   
   The PR also fixes the snowflake `account_identifier` used in the hook which 
used to force a region, but region should be 
[optional](https://docs.snowflake.com/en/user-guide/admin-account-identifier) 
in the identifier. 
   
   Also tested locally by running the `SnowflakeSqlApiOperator` operator in 
example DAG.
   
   closes: https://github.com/apache/airflow/issues/36621
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


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