jedcunningham commented on PR #61436: URL: https://github.com/apache/airflow/pull/61436#issuecomment-3855088718
> Even though it's pointed out as bad practice as This just formalizes that it's best practice to have triggers come from elsewhere on sys.path instead to avoid that problem. in https://github.com/apache/airflow/pull/48603 > > From the user perspective, I would expect my triggers defined in Dag files could be imported by Triggerer, but the Triggerer doesn't respect AIRFLOW__CORE__DAGS_FOLDER currently. Don't focus as much on my PR description, but the changes in the PR. It's not just "best practice" not to in Airflow 3, we intentionally removed the ability to have them in a dag file. Also, don't focus on "dags folder" - you must have a multi-bundle mental model now. The "dags folder" config is simply a default for familiarity sake. It is completely valid to have a deployment that does not use `[core] dags_folder` at all, and any change referencing it directly should immediately raise a yellow flag :) -- 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]
