nan0o opened a new issue, #27598:
URL: https://github.com/apache/airflow/issues/27598
### Apache Airflow Provider(s)
apache-beam
### Versions of Apache Airflow Providers
_No response_
### Apache Airflow version
2.3.3
### Operating System
Not sure what OS GKE Pods use
### Deployment
Composer
### Deployment details
_No response_
### What happened
When using BeamRunPythonPipelineOperator, composer shows in the task logs
that it's trying to use "google_cloud_default" as a connection id even though I
specify in the operator that it should be "dataflow_conn"
### What you think should happen instead
Use "dataflow_conn" as the connection id
### How to reproduce
BeamRunPythonPipelineOperator(
task_id='xxxx',
runner="DataflowRunner",
# This doesn't work even though the docs
# indicate you should pass this to the constructor
#gcp_conn_id='dataflow_conn',
py_file=f'/home/airflow/gcs/data/{project_name}/main.py',
pipeline_options={
'project_id': project_id,
'input_path': input_path,
'output_path': output_path,
'schema_path': schema_path,
'service_account': service_account,
'no_use_public_ips': True,
'subnetwork': subnetwork,
'staging_location': staging_location,
'temp_location': temp_location,
"setup_file": f'/home/airflow/gcs/data/{project_name}/setup.py',
"machine_type": "n1-standard-4",
"num_workers": 5,
"max_num_workers": 10,
},
py_options=[],
py_interpreter='python3',
py_system_site_packages=False,
dataflow_config=DataflowConfiguration(
job_name='{{task.task_id}}',
location=gce_region,
wait_until_finished=False,
# This works for some reason!
gcp_conn_id="dataflow_conn"
),
)
### Anything else
_No response_
### Are you willing to submit PR?
- [ ] 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]
