New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rules/Request: Airflow DAGs checks #4421
Comments
The rules defined in https://github.com/BasPH/pylint-airflow seem to cover all those cases plus a bit more. Would a port of that Pylint plugin be a good start? |
Bas' pylint-airflow is definitely a good start, but worth noting it was designed for Airflow 1.x and we should aim to get ruff supporting Airflow 2.x, so there are likely a few changes we'll want to make. Maybe I can open a draft PR with a few of the easy rules (no duplicate DAG names, no empty DAGs, etc) to get something going, and then we can open issues for specific rules afterwards? @charliermarsh - what do you think? |
@jlaneve - Yeah, that's perfect. |
Exactly - I had seen |
https://docs.astronomer.io/learn/dag-best-practices Some opinionated options (which could certainly be contentious):
|
Some Astronomer folks might be able to help development :) |
Is there a roadmap timeline for this? |
what essentially makes the difference between ruff check vs ruff lint |
@usethia your question seems unrelated to this issue. I'll reply anyway but please open a new issue if you need more help to avoid sidetracking this issue.
To lint your project, run |
There are numerous problems that could go wrong with an Airflow DAG, ex:
Seems like we might want new rules that could be used to detect these things.
The text was updated successfully, but these errors were encountered: