Thanks for pointing out solutions I hadn't considered. > we could simply have a pytest fixture that will do the job (based on what > Daniel proposed). > It will not support running tests via Airflow UI or regular python execution > of the test files, > but maybe it's a good idea that does not rely on docker/breeze.
I like the idea that example dags are actual dags, that you can drop in your dags folder and run (provided you have the right config). As you mention, adding a pytest fixture to run the triggerer will probably break that ? It'd also break the setup Phani described __, if I understood correctly ? >> Our approach is to spin up Airflow , install the providers that currently >> have deferrable functionality, >> and run system tests on those example DAGs So I'd be in favor of adding a flag to breeze to start a triggerer. It's the most flexible option, lets people run tests in full airflow, in breeze, or outside of breeze by running the triggerer themselves. It also sounds like it wouldn't be too hard to implement, even though I'm not familiar with breeze code. I can try to give it a shot later this week or the next. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
