msumit commented on issue #24464: URL: https://github.com/apache/airflow/issues/24464#issuecomment-2969634697
> How about having the Folder(Group) Dags based on their actual file directory, then it seems like we could achieve this by simply adding a new UI endpoint that: > > * Parses the first-level directory prefix > * Groups DAGs accordingly > > If users want to change the group, they could just move the DAG file to a different directory. -1 for real path-based hierarchies. A couple of reasons from the top of my mind are: - The paths where the real DAG gets generated could be long and nasty - Many orgs created frameworks like a single python file is reading from some yaml/json config and generating thousands of dags, so all of them would become part of the same folder. Though they belong to diff teams and solving diff usecases. However, if we go via tag-based structure, it won't be an issue. Infact, we can treat real paths also as a tag (behind a config setting), so those who wants path level structure, it'll be available to them. -- 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]
