suhail-zemoso commented on issue #53617: URL: https://github.com/apache/airflow/issues/53617#issuecomment-3112913108
I went through the official documentation and tested with both versions 3.0.3 and 3.1.0. When running the airflow info command, I noticed that the DAGs path is not listed there. However, the documentation provides two workarounds to import custom modules into DAG files: Create the module inside the plugins directory and import it into your DAG files. Manually add the DAGs folder to the PYTHONPATH. In my case: dags_folder: /files/dags plugins_folder: /files/plugins To test the import flow, I created a module with a dummy function inside the /files/plugins directory. I then imported this module into a DAG file located in the DAGs folder. The DAG was successfully detected in the UI, and I was able to trigger it. I verified the logs and observed the expected output. I hope these findings are helpful. If you have any questions or need further clarification, please feel free to reach out. -- 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]
