New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates to FlaskAppBuilder 3.3.2+ #17208
Conversation
6256f00
to
dd4a1ab
Compare
dd4a1ab
to
c722557
Compare
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
REbuilding |
c722557
to
12a2311
Compare
I was hoping this would get us to SQLAlchemy 1.4, but alas it is not to be 😞 |
Ah.I have to fix this failure, to |
Eh! It's actually a bug! We are running helm tests against LATEST images from ghcr.io, not the ones from latest sources! Fix is coming! |
There was a bug in our CI - Kubernetes tests were executed running lates ghcr.io image, rather than the image built from sources of the current PR. This PR fixes it by correctly using the PR commit as tag of the image used as base image for kubernetes tests. (cherry picked from commit 4796675)
When k8s virtualenv is prepared to run k8s tests we are using constraints, this however might lead to a problem when we increase minimum version of an affected dependency and it conflicts with the constraints stored in main. Therefore in case we run tests in CI (which is indicated by specific pull tag that we use) we do not use constraints for installing the kubernetes venv. It should be fine, as we are pretty much running this only as a vehicle to run tests. (cherry picked from commit e3d7e68)
There are some clarifications about using the authentication via FlaskAppBuilder - the change implements minimum version of the FAB to 3.3.2 and clarifies the dependencies used in FAB 3 series to be only authlib rather than flask-oauth. Fixes: apache#16944 (this is the second, proper fix this time). Depends on: apache#17290, apache#17289 - those two errors have been detected while analysing failures in this build.
12a2311
to
84ff29b
Compare
There are some clarifications about using the authentication via FlaskAppBuilder - the change implements minimum version of the FAB to 3.3.2 and clarifies the dependencies used in FAB 3 series to be only authlib rather than flask-oauth. Fixes: apache#16944 (this is the second, proper fix this time). (cherry picked from commit 6d7fa87)
There are some clarifications about using the authentication via FlaskAppBuilder - the change implements minimum version of the FAB to 3.3.2 and clarifies the dependencies used in FAB 3 series to be only authlib rather than flask-oauth. Fixes: apache#16944 (this is the second, proper fix this time). (cherry picked from commit 6d7fa87)
There are some clarifications about using the authentication via FlaskAppBuilder - the change implements minimum version of the FAB to 3.3.2 and clarifies the dependencies used in FAB 3 series to be only authlib rather than flask-oauth. Fixes: #16944 (this is the second, proper fix this time). (cherry picked from commit 6d7fa87)
There are some clarifications about using the authentication via FlaskAppBuilder - the change implements minimum version of the FAB to 3.3.2 and clarifies the dependencies used in FAB 3 series to be only authlib rather than flask-oauth. Fixes: #16944 (this is the second, proper fix this time). (cherry picked from commit 6d7fa87)
There are some clarifications about using the authentication
via FlaskAppBuilder - the change implements minimum version of the
FAB to 3.3.2 and clarifies the dependencies used in FAB 3 series
to be only authlib rather than flask-oauth.
Fixes: #16944 (this is the second, proper fix this time).
Depends on: #17290, #17289 - those two errors have been detected while
analysing failures in this build.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.