sanederchik commented on issue #50020: URL: https://github.com/apache/airflow/issues/50020#issuecomment-2850615737
I think you misunderstood a little bit my point, so I'd like to clarify, sorry if I had missled you before. Your example from docs shows dynamic DAG generation where all DAG config and creation process is provided within single DAG file. And it is very good for creating several DAGs from one script file with the same structure but different configs. However in production environment it may be convenient to add an additional layer of abstraction by moving DAG generation config, tasks, etc. to separate modules. And then reuse them either in dynamic DAGs generation, like in example in docs, or in single DAG generation like in my example. Additionally, it becomes easier to cover a "reusable DAG" with tests. So the main point of my issue is about creating `reusable DAG` modules, not about only dynamic DAG generation (but of course it's the main way to use it). -- 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]
