amoghrajesh commented on code in PR #44720: URL: https://github.com/apache/airflow/pull/44720#discussion_r1873477494
########## contributing-docs/11_provider_packages.rst: ########## @@ -28,8 +28,8 @@ Airflow 2.0 is split into core and providers. They are delivered as separate pac Where providers are kept in our repository ------------------------------------------ -Airflow Providers are stored in the same source tree as Airflow Core (under ``airflow.providers``) package. This -means that Airflow's repository is a monorepo, that keeps multiple packages in a single repository. This has a number +Airflow Providers are stored in the separate tree than Airflow Core (under ``providers`` directory). Review Comment: ```suggestion Airflow Providers are stored in a separate tree other than the Airflow Core (under ``providers`` directory). ``` ########## contributing-docs/11_provider_packages.rst: ########## @@ -89,6 +89,19 @@ and pre-commit will generate new entry in ``generated/provider_dependencies.json ``pyproject.toml`` so that the package extra dependencies are properly handled when package might be installed when breeze is restarted or by your IDE or by running ``pip install -e ".[devel]"``. +Chicken-egg providers +--------------------- + +Sometimes, when provider depends on another provider, you might want to add a new feature that spans across +two providers. In this case, you might need to add a new feature to the "dependent" provider, but you need +to add a new feature to the "dependency" provider as well. This is a chicken-egg problem and by default Review Comment: ```suggestion Sometimes, when a provider depends on another provider, and you want to add a new feature that spans across two providers, you might need to add a new feature to the "dependent" provider, you need to add a new feature to the "dependency" provider as well. This is a chicken-egg problem and by default ``` -- 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]
