Apache Airflow Provider(s)
databricks
Versions of Apache Airflow Providers
apache-airflow-providers-databrick 6.9.0
Apache Airflow version
2.9.2
Operating System
Amazon Linux 2023
Deployment
Amazon (AWS) MWAA
Deployment details
No response
What happened
Templates/macros defined in DatabricksNotebookOperator inside DatabricksWorkflowTaskGroup are passed to Notebook as template text, not as an expected value.

What you think should happen instead
Resolution happens on task execution. But Databricks job is already created at that moment
How to reproduce
If you define notebook_params in DatabricksWorkflowTaskGroup templates will be resolved, if in DatabricksNotebookOperator inside DatabricksWorkflowTaskGroup - not resolved.
In provided part of DAG (unrelated removed) param1 correctly passed to notebook, but param2 passed as {{ ds }}
with DatabricksWorkflowTaskGroup(
...
notebook_params={"param1": "{{ ds }}"},
) as tg:
task1 = DatabricksNotebookOperator(
...
notebook_params={"param2": "{{ ds }}"},
)
Anything else
No response
Are you willing to submit PR?
Code of Conduct
Apache Airflow Provider(s)
databricks
Versions of Apache Airflow Providers
apache-airflow-providers-databrick 6.9.0
Apache Airflow version
2.9.2
Operating System
Amazon Linux 2023
Deployment
Amazon (AWS) MWAA
Deployment details
No response
What happened
Templates/macros defined in DatabricksNotebookOperator inside DatabricksWorkflowTaskGroup are passed to Notebook as template text, not as an expected value.

What you think should happen instead
Resolution happens on task execution. But Databricks job is already created at that moment
How to reproduce
If you define notebook_params in DatabricksWorkflowTaskGroup templates will be resolved, if in DatabricksNotebookOperator inside DatabricksWorkflowTaskGroup - not resolved.
In provided part of DAG (unrelated removed) param1 correctly passed to notebook, but param2 passed as
{{ ds }}Anything else
No response
Are you willing to submit PR?
Code of Conduct