diff --git a/contributing-docs/11_provider_packages.rst b/contributing-docs/11_provider_packages.rst index 1b70d91205dae..e96d5e40d4160 100644 --- a/contributing-docs/11_provider_packages.rst +++ b/contributing-docs/11_provider_packages.rst @@ -36,9 +36,17 @@ repository and project. It has also some disadvantages as this introduces some coupling between those - so contributing to providers might interfere with contributing to Airflow. Python ecosystem does not yet have proper monorepo support for keeping -several packages in one repository and being able to work on multiple of them at the same time, but we have -high hopes Hatch project that use as our recommended packaging frontend -will `solve this problem in the future `__ +several packages in one repository and being able to work on more than one of them at the same time. The tool ``uv`` is +recommended to help manage this through it's ``workspace`` feature. While developing, dependencies and extras for a +provider can be installed using ``uv``'s ``sync`` command. Here is an example for the microsoft.azure provider: + +.. code:: bash + + uv sync --extra devel --extra devel-tests --extra microsoft.azure + +This will synchronize all extras that you need for development and testing of Airflow and the Microsoft Azure provider +dependencies including runtime dependencies. See `local virtualenv <../07_local_virtualenv.rst>`_ or the uv project +for more information. Therefore, until we can introduce multiple ``pyproject.toml`` for providers information/meta-data about the providers is kept in ``provider.yaml`` file in the right sub-directory of ``airflow\providers``. This file contains: