bugraoz93 commented on issue #49330: URL: https://github.com/apache/airflow/issues/49330#issuecomment-2810593637
> @bugraoz93 , I have been testing airflow 3.0.0rc2 for a couple of days when I noticed this. So you are saying the only way to reflect the true state of the dags in a "out of the box/local" setting is to spin up a dag-processor in that local setup and then run the cli commands? > > Don't you think we should add a --local arg ( or something similar ) to the `list` and `list-import-errors` to be able to iterate on during dag development in user's local areas? Yes, exactly for Airflow 3.0+. I don’t think that should be needed. How are you testing locally? If you are using Breeze, the `start-airflow` command should already run the standalone Dag Processors. Or if you are using docker-compose or helm charts in minikube or so. It should be already running out of the box. Breeze https://github.com/apache/airflow/blob/main/dev/breeze/doc/03_developer_tasks.rst Compose https://github.com/apache/airflow/blob/84cd1d6eb25fa2c9484c4310fdbab037e6f19924/airflow-core/docs/howto/docker-compose/docker-compose.yaml#L155 Helm https://github.com/apache/airflow/blob/84cd1d6eb25fa2c9484c4310fdbab037e6f19924/chart/templates/dag-processor/dag-processor-deployment.yaml#L21 -- 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]
