[GitHub] [airflow] mobuchowski commented on issue #33909: Split out providers into "standalone" python packages

["mobuchowski (via GitHub)" <gi...@apache.org>]

mobuchowski commented on issue #33909:
URL: https://github.com/apache/airflow/issues/33909#issuecomment-1698815790

   I like providers being standalone packages by default. In addition to the benefits described here, it would allow installing providers straight from github via pip. 
   
   I agree with @uranusjr that being a monorepo instead of multiple separate repos is a net benefit, especially when also thinking about local development process, not only CI.
   
   >Ideal workflow of the developer is where they can:
   >    run breeze and be able to edit any sources locally in the host - and airflow in breeze should automatically pick the changes in both airlfow and providers when interpreter is started
   >    install a local venv (in editable mode possibly) for airlfow and selected (all?) providers and the locally installed airflow should also pick changes for both airflow and providers when interpreter is started
   
   
   Ideally, there would also be no functional differences between Airflow running this way, and production image of Airflow - besides selection of installed/running providers.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org