-
Notifications
You must be signed in to change notification settings - Fork 16.3k
remove the 'provide_authorized_glcoud' from BeamPipeline operators #55453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+23
−32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396
bbd8430 to
ebf2234
Compare
potiuk
approved these changes
Sep 10, 2025
suman-himanshu
pushed a commit
to suman-himanshu/airflow
that referenced
this pull request
Sep 17, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
Brunda10
pushed a commit
to Brunda10/airflow
that referenced
this pull request
Sep 17, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
78 tasks
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Sep 30, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 1, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 2, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 3, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 4, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 7, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 8, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 9, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 10, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 11, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 12, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 14, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 15, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 17, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 19, 2025
…pache#55453) - As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow. - There is known bug (apache#42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself. closes: apache#42396 Co-authored-by: Oleg Kachur <kachur@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As durng the operator execution we launch cmd calling beam tool with the dataflow runner it fully cappable to work with standard google credentals, so no need to set them manually here, more over the authorized gcloud session has no use running beam on dataflow.
There is known bug (BeamRunPythonPipelineOperator doesn't work with Google Application Default Credentials ADC #42396), where calling the provide_authorized_gcloud disrupts the ADC lookup for the beam itself.
closes: #42396
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.