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

   ### Apache Airflow version
   
   2.2.5
   
   ### What happened
   
   I have a dag that starts another dag with a conf.   When the driving dag is 
rerun and it produces a different conf for the same trigger_dag_id the new conf 
is not supplied to the called dag.
   
   
   code block:
                   logging.info(f"starting {row.file_id} , {row.file_name}")
                   t = TriggerDagRunOperator(trigger_dag_id=process_dag_id,
                                             task_id='starter',
                                             trigger_run_id=prefix,
                                             reset_dag_run=True,
                                             **conf={"file_id": row.file_id,
                                                   "file_name": row.file_name,
                                                   "feed_type": feed_type
                                                   },**
                                             wait_for_completion=False,
                                             execution_date=row.created_ts + 
timedelta(
                                                 microseconds=row.process_slot)
                                             )
                   t.execute(context)
   
   ### What you think should happen instead
   
   I should use the new conf when starting the called dag
   
   ### How to reproduce
   
   Seems ovious 
   
   ### Operating System
   
   windows and ubuntu
   
   ### Versions of Apache Airflow Providers
   
   N/A
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### 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]

Reply via email to