fpopic opened a new issue, #42396:
URL: https://github.com/apache/airflow/issues/42396

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.6.3
   
   ### What happened?
   
   When manually submitting the most straightforward beam python job to Google 
Dataflow runner 
   
   WITHOUT specifying as operator parameter
   - `service_account_name`
   
   WITHOUT having any explicit environment variable set
   - `GOOGLE_APPLICATION_CREDENTIALS`
   - `GCP_PROJECT`
   
   WITH using only:
   - `gcloud auth application-default login`
   - `gcloud config set project`
   
   Airflow get stuck in apitools that use under the hood **oauth2client** 
instead of recommended **google-auth** 
https://github.com/google/apitools/blob/v0.5.32/apitools/base/py/credentials_lib.py#L551-L552
   
   
   
   ### What you think should happen instead?
   
   Airflow should submit job to Dataflow using Application Default Credentials 
the same way standalone Apache Beam Python submits the job to Dataflow without 
any issue.a 
   
   ### How to reproduce
   
   Preapre your enviornment
   
   ```
   unset GOOGLE_APPLICATION_CREDENTIALS
   unset GCP_PROJECT
   gcloud auth application-default login
   gcloud config set project
   ```
   
   ### Operating System
   
   macOS 14.7
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-apache-beam==5.3.0
   
   ### Deployment
   
   Google Cloud Composer
   
   ### Deployment details
   
   - composer-2.5.1-airflow-2.6.3
   - python 3.8.12
   
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.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