pierrejeambrun commented on PR #41896: URL: https://github.com/apache/airflow/pull/41896#issuecomment-2324186024
> I think for Airflow 3 development, it's quite ok to keep things separate, but agree with @jscheffl that it should be unified eventually. I think we should get rid of all the old connexion thing - having all the experience with connexion 3 and convert all our APIs and websever endpoints to use FastAPI - looking at how much it handles for us, and the fact that we can make some incompatibility decisions made in Airflow 2 for the APIs (error handling for one, base_url handling etc.) - having a single, unified FastAPI (even if opinionated and with different decieions) is a great opportunity to "standardising" our UI work - that would need some work on converting existing REST endpoints (and especially tests) to use Fast API, but other that potential slight incompatibilities, I do not see any problems with it. Fast API can generate OpenAPI spec from the code, get swagger conected and so on and we can make it works "slightly differently" for airlfow 3 - and migrate the code for our cur rent REST API gradually. But it does not have to be "now". > I'd say - migrating existing REST APIs to the new "ui-api" command is the way to go. Totally agree. At the end of the day we want a standardized way of handling our Rest API, code first, most likely all FastAPI. And we will migrate the existing for airflow 3 development. Then the new RestAPI can be a drop in replacement for the existing plublic API that will be completely removed I suppose. -- 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]
