[GitHub] [airflow] mjpieters commented on pull request #11596: Allow loading plugins on Airflow start-up
mjpieters commented on pull request #11596: URL: https://github.com/apache/airflow/pull/11596#issuecomment-710478877 Another workaround is to just import these items directly, not from the `airflow.(hooks|operators|sensors).` namespace. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [airflow] mjpieters commented on pull request #11596: Allow loading plugins on Airflow start-up
mjpieters commented on pull request #11596: URL: https://github.com/apache/airflow/pull/11596#issuecomment-710474026 TBH, the lack of plugin loading in the scheduler _annoying_. I can also add ```python from airflow import plugins_manager plugins_manager.ensure_plugins_loaded() ``` to any DAG that needs to have access to plugin-provided operators, sensors or hooks, I suppose. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [airflow] mjpieters commented on pull request #11596: Allow loading plugins on Airflow start-up
mjpieters commented on pull request #11596: URL: https://github.com/apache/airflow/pull/11596#issuecomment-710463154 Looks like I'll need this switch? We have dags that use plugin operators & sensors, and the scheduler fails to load our dags as the plugin is not loaded when processing each file. So `airflow dags list` works, `airflow dags show ` works, the webserver is able to show all the dags, but the `import_error` table shows that the _scheduler_ (or rather, the `DagFileProcessorProcess` job), can't load our dags due to the missing plugins. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org