dheerajturaga commented on issue #49330: URL: https://github.com/apache/airflow/issues/49330#issuecomment-2811044387
If you look at it from a newbie dag author perspective, you dont have any services running nor do you intend to deploy Airflow3 service either. You just have access to a dags dir and a airflow install (cli) through venv. Airflow 2 can simply list my import errors without needing to have any service up and running. Airflow 3 requires me to have a `dag processor` running which is unnecessary when someone is developing their dags and just want to check for syntax issues. ( This setup is not for official deployment but for local dag development) I am aware that standalone does launch all services but having to run a whole service to simply check syntax issues and list dags I have in my dagbag seems overkill. I have a PR in the pipeline which adds back the original functionality with the `--local` option. Please review it once I push -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
