potiuk commented on issue #33909: URL: https://github.com/apache/airflow/issues/33909#issuecomment-1698619441
Another thought.... Maybe we do NOT have to solve the challenge of all-editable build for airflow for providers. I think we have a viable alternative.... * Breeze could remain an all-editable environment even after we move the providers to subfolders. It could read all the dependency information from pyproject.toml files instead of provider.yaml files (we can very easily change the way how `generated/provider_dependencies.json` are generated * When/If we get to contributing @kaxil's `airflowctl` to become our "community" tool eventually- We could use it to have an easy local venv to install "airflow" in it and add an easy way to "inject" provider's editable sources (selected or all) and dependencies into such environment. While `airflowctl` is mainly targeted to support DAG development, we could make it easy to "inject" editable sources of providers too. That would be even better than what we have now - because contributors could test new providers also with old airflow version very easily (it's not easy currently). Breeze could remain the "CI" driver and "All-editable" sources where latest source airflow + latest providers could be developed and tested (which is absolutely necessary BTW). Also cc: @mobuchowski and @hussein-awala as I know they are interested in DevEX and I think it would be great to do some discussion/brainstorming running about that and potential future changes to it in a bit more of an "interest group". Of course others are invited too. We could design together the future of Airflow dev-env for that and once we have the providers as "standalone" packages, we could then start a discussion "Does it make sense/ Do we want to split providers to a separate repo". I have no ready answer for that (lots of thoughts though). But I think this dicussion should happen after we have the providers as "standalone" packages in our main "monorepo". -- 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]
