Vincent
Vincent
@ashb @potiuk Question for you. Since we want to create a new major version of FAB provider that would only be compatible with Airflow 3, I do not need to...
Ready for review @pierrejeambrun
> If that's too much work, we can at first only support JWT Oauth for the new API (both public and UI). And add more backends in 3.x. I don't...
Static checks are failing, running the pre-commit should auto resolve them
Yep I think it is needed. But we might actually want only core changes, breaking change in providers will result in creating major versions which we might not want yet....
@dirrao Could you please update this PR (or create another one) to include only changes from core?
Actually I think your changes are fine. It seems inevitable to force Airflow 3 to use the latest FAB version provider. See comment [here](https://github.com/apache/airflow/pull/42042#issuecomment-2333313742). If that is the case your...
> The commit message says removed deprecation but this PR also adds more functionality to the provider. Is the commit message right? The only code added to the provider is...
Yeah I tried in #43081 but could not make it work. Mypy/Python is not happy about it and raise a `SyntaxError`
Is there any chance you could split up this PR in multiple PRs? 15k lines of code is really hard to review :)