Lee-W commented on issue #41641: URL: https://github.com/apache/airflow/issues/41641#issuecomment-2507263054
> > For people bypassing the python client and making direct request to the API (or any other non-python system), we can indeed catch errors of such breaking change and return a clear message that this is not accepted anymore, and maybe even better give them the new way of how to achieve this. It's just more work but possible. > > Just to repeat above - yes. I think it's more work, and I think it might require some nasty workarounds in FAST API that we will have to keep forever, but **maybe** we can do a 2.11-only change that will raise warnings if the old way is used instead (and allow to use new way) ? Not sure if possible and how many such breaking channges we will have, but it would really be nice to tell the users "if you have no warnings on 2.11, you are good to go". I just tried to follow the API discussion 🙌 so we're now doing 1. warning if they're using airflow python client 2. return an error and guide in FastAPI but wouldn't it be easier for us to do only the second one and solve it all at once? Should we trace those API changes only in https://github.com/apache/airflow/issues/43378? -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
