anavrotski opened a new issue, #70121: URL: https://github.com/apache/airflow/issues/70121
### Under which category would you file this issue? Providers ### Apache Airflow version 3.3.0 ### What happened and how to reproduce it? The change introduced by https://github.com/apache/airflow/pull/66613 (for https://github.com/apache/airflow/issues/39002) makes DatabricksRunNowOperator always include DAG-level params as job_parameters. Since apache-airflow-providers-databricks 7.16.0, users cannot opt out of passing those parameters, which creates compatibility issues for Databricks jobs whose entry point does not expect or accept them. ### What you think should happen instead? DatabricksRunNowOperator should provide a way to opt out of forwarding DAG-level params as job_parameters. Automatically injecting self.params changes the job payload and can break existing jobs that do not expect those parameters. The default behavior should either remain unchanged for backward compatibility or provide an explicit flag controlling parameter propagation. ### Operating System _No response_ ### Deployment Official Apache Airflow Helm Chart ### Apache Airflow Provider(s) databricks ### Versions of Apache Airflow Providers apache-airflow-providers-databricks 7.16.0 ### Official Helm Chart version 1.21.0 ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _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]
