jgoedeke commented on issue #57498:
URL: https://github.com/apache/airflow/issues/57498#issuecomment-3466485732
For my usecase I do not see any benefit from having the DAG params within
every `HITLOperator`.
I found some more strange behavior:
1. It is not possible to override the value of a DAG param.
2. Param values are not templated, therefore I can not use the DAG param
value as default for another field. This is important in case DAG params should
not be inserted into HITLOperator params in the future.
```python
HITLOperator(
task_id='task_with_more_params',
subject='Please choose an option:',
options=['Option X', 'Option Y'],
params={
'task_param': 'value',
'dag_param1': 'This does not override the dag_param1',
'tempalted_param': '{{ dag_run.conf.get("dag_param2") }}',
},
)
```
<img width="1178" height="563" alt="Image"
src="https://github.com/user-attachments/assets/03320f27-eff9-4a89-a1a2-b93108ccb9fd"
/>
If possible I would prefer an optional to include DAG Params in the Operator
with a flag like `include_dag_params: bool = False`.
--
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]