pierrejeambrun commented on PR #41957: URL: https://github.com/apache/airflow/pull/41957#issuecomment-2325806974
[bugraoz93](https://github.com/bugraoz93) I would that the initial idea is to just migrate existing endpoints to the new API (FastAPI), modifying only endpoints if necessary so we can re-wire the old UI on new endpoints and be sure that things are working as expected. Also this will minimize the migration effort. Then we can take airflow 3 opportunity to bring any breaking change that we need to the public part of the API if we feel like the restructuration should be done. I am not sur we are fully ready to start the migration yet. Very close for 'private' endpoints i.e `/objects` but for the public one I will still need to figure out the `auto-generation` part of front end code. (types). I would say that we can start migrating once: - Permissions are handled in the new API so we can also move the existing permission set to the new UI - UI is re-wired on this new API (so we can safely delete the old endpoint and minimize code duplication) > I think it's a good topic to discuss at the next dev call (this Thursday) I'll try to write the documentation down by then, and If we are happy with it and agree with the general strategy I can present it to the rest of the community. -- 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]
