GitHub user cesar-vermeulen created a discussion: Reflect breaking changes in Azure Data Factory operator, sensor and triggerer
### What do you see as an issue? Since PR https://github.com/apache/airflow/pull/34040/files, factory_name and resource_group_name have become required keyword arguments. This is however not reflected in the documentation: https://airflow.apache.org/docs/apache-airflow-providers-microsoft-azure/stable/operators/adf_run_pipeline.html As well as in the docstring (even providing faulty information; we can not use the extra properties in the data factory connection anymore thus leading to confusion): https://github.com/apache/airflow/blob/522576b9c0c04039d30a01757f0990dbaf72a425/airflow/providers/microsoft/azure/operators/data_factory.py#L91C11-L91C12 ### Solving the problem Adapt documentation so that it becomes clear that resource group name and factory name are now required keyword arguments. Might need further investigation of why this has become a required keyword arguments whilst keeping the functionality in the hook to default to getting the RG name and factory name from the Airflow connection (https://github.com/apache/airflow/blob/522576b9c0c04039d30a01757f0990dbaf72a425/airflow/providers/microsoft/azure/hooks/data_factory.py#L76) ### 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) GitHub link: https://github.com/apache/airflow/discussions/63196 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
