jscheffl commented on issue #52469: URL: https://github.com/apache/airflow/issues/52469#issuecomment-3448517589
> When you say is to be implemented as feature, do you mean something like... The current breeze CLI with `--load-example-dags` just globally loads examples. I would keep it simple at first and with this flag load all examples from all providers (and assuming core examples are not existing in core in the future but all will be hosted in standard provider). Then the examples automatically vary depending on which providers are installed. If then in future people think this is overwhelming, then a filter switch can be added later as increment as well. > Now I'm again at the crossroads: Should we load both dagbag collect_dags and Dagbundle, and which is used when? That is a very good question. I have no strong opinion but using the Bundle mechansim looks like a superior way compared to loading examples from a hard-wired folder. And if we want to load from multiple folders the way of defining a Bundle per provider looks like a good approach. I'd also favor an opinion from @jedcunningham but he is on leave atm. Is Dagbag noch indirectly loading the bundles as well? I am not too much into this detail but might be a good chance to clean-this up on a general level as tests should use the "normal" mechanisms. Maybe a fixture is needed to load the corresponsing test Dags into the testing environment. -- 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]
