potiuk commented on issue #31200: URL: https://github.com/apache/airflow/issues/31200#issuecomment-1548288536
> I'm not sure that this is possible to achieve with the current airflow jobs check. For sure you can do it with an API. Or maybe this is a great idea to contribute such check to Airflow. This is the only way to make sure that anything you do there is not going to change in the next version. If you do not have unit tests covering it and making sure that regression tests are passing, there is no way we can maintain backwards compatibility of the code. If yuou have not made any effort (by adding and making sure that the tests are in Airflow that can guarantee something, we are not able to promise absolutely anything. This is one of the reasons why the bug crept into 2.6.0 - because it had no test to prevent regressions - now it has https://github.com/apache/airflow/pull/31277/files#diff-9499319fda165fa31190eba1879d7ecf71871ce3536da0a8505ba529378095c7R151 It would be absolutely unreasonable to expect that things will not change - code is a living thing. And what Airflow team can do is to promise that will make all the effort to keep the things that are public interface backwards compatible. And this is what [public interface of Airflow](https://airflow.apache.org/docs/apache-airflow/stable/public-airflow-interface.html) document is about. Look there. If you find something that is not there, don't rely on it. Even more if you find that something is specifically excluded (like direct DB access) - don't use it even more. Figure a different way (Stable REST API is a good idea). Just stick to it. There is no argument about it anyway, until you bring the diccussion into the devlist and convince the people to change their decision about it. You have to change your ways or things will break. You have been warned (for the third time). And just to make a bit more illustration of what you are asking for. I know it's largely exaggerated and what you want is no not as extreme as this but the line of thinking you have here is very similar to this one:  But with Airlfow explicitly defining what is public interface and what is not, you are basicaly asking for this^^ -- 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]
