aymericbbc opened a new issue #21665:
URL: https://github.com/apache/airflow/issues/21665


   ### Apache Airflow Provider(s)
   
   google
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-apache-beam==3.1.0
   apache-airflow-providers-cncf-kubernetes==2.1.0
   apache-airflow-providers-ftp==2.0.1
   apache-airflow-providers-google==5.1.0
   apache-airflow-providers-hashicorp==2.1.1
   apache-airflow-providers-http==2.0.1
   apache-airflow-providers-imap==2.0.1
   apache-airflow-providers-postgres==2.3.0
   apache-airflow-providers-sendgrid==2.0.1
   apache-airflow-providers-sqlite==2.0.1
   apache-airflow-providers-ssh==2.3.0
   
   ### Apache Airflow version
   
   2.2.3 (latest released)
   
   ### Operating System
   
   linux
   
   ### Deployment
   
   Composer
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   When executing [this 
operator](https://github.com/apache/airflow/blob/main/airflow/providers/google/cloud/operators/dataflow.py#L163),
 a dataflow job is created with a random suffix. This random suffix doesn't 
allow my team to monitor a given dataflow job scheduled every day because the 
name is changing every day
   
   ### What you expected to happen
   
   I would expect to have the option to have full control on dataflow job name 
to be able to monitor all jobs with the same name
   
   ### How to reproduce
   
   Execute a task with this operator twice
   
   ### 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