r-richmond commented on PR #70446: URL: https://github.com/apache/airflow/pull/70446#issuecomment-5956186135
> Does this need a new CLI command? The Dag processor already detects version inflation (`[dag_processor] dag_version_inflation_check_level`), the FAQ describes diffing `serialized_dag` rows, and ruff's AIR304 catches the common causes statically. An `airflow dags stability` command is permanent CLI surface, and `--fail-fast` can only trigger on the last of the two parses, so it has no effect. Is there an issue or a user asking for this? Converting to draft until there is. I would be a user asking for this, although I did jump on after it was submitted. See my comment https://github.com/apache/airflow/pull/70446#issuecomment-5159593952 here for my motivation. Note: We are currently running 3.3.1 and `dag_version_inflation_check_level` did not catch the issue that caused our version number to explode and as mentioned before neither did AIR304. TLDR this command would fit perfectly in our CI/CD and seems to be the most rubout solution yet. -- 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]
