-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Move access_denied_message webserver config to fab #50208
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
Move access_denied_message webserver config to fab #50208
Conversation
2df9a68
to
34530a7
Compare
34530a7
to
e5e91ac
Compare
Changing the milestone to 3.0.2 -- about to cut 3.0.1 |
d491f5e
to
81ffc76
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code changes provider and core at the same time. How if somebody uses the old core and a new FAB? Are you sure it is not breaking?
I think Jens is right, but on the other side: if you use Airflow 3.0.2 (next version of Airflow not yet released that includes this change) and FAB 2.0.2 (version of FAB provider already released, NOT containing this change), then We already have in
Should we bump it up to |
If we really want to set min version of FAB then no - we do not have to wait- we can add >2.0.3 AND update fab provider in the same PR to be 2.0.3 . This should all work |
Thanks for the review guys. I have updated dependencies:
This way basically fab Also updated to core 3.0.2 the |
* bump Airflow to 3.0.1 * remove common.messaging from the list of removed providers * add fab to the list of removed providers in anticipation of the apache#50208
* bump Airflow to 3.0.1 * remove common.messaging from the list of removed providers * add fab to the list of removed providers in anticipation of the apache#50208
The compat tests shoudl be fixed after we merge #50537 |
* bump Airflow to 3.0.1 * remove common.messaging from the list of removed providers * add fab to the list of removed providers in anticipation of the #50208
f2b9486
to
5f094b5
Compare
#50537 has been merged, rebasing |
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker a18a1df v3-0-test This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
* Move access_denied_message webserver config to fab * Fix CI * Update to fab 2.0.3 * Change core to 3.0.2 * fab depends on apache-airflow 3.0.2 * Fix CI (cherry picked from commit a18a1df)
Cherry picking PR here #50544 |
* Move access_denied_message webserver config to fab * Fix CI * Update to fab 2.0.3 * Change core to 3.0.2 * fab depends on apache-airflow 3.0.2 * Fix CI (cherry picked from commit a18a1df)
… (#50544) * Move access_denied_message webserver config to fab (#50208) * Move access_denied_message webserver config to fab * Fix CI * Update to fab 2.0.3 * Change core to 3.0.2 * fab depends on apache-airflow 3.0.2 * Fix CI (cherry picked from commit a18a1df) * Fix CI * docs: conditionally render section‐move links in sections‐and‐options include (#50582) * Add condition for section move in docs * docs(fab): add Sphinx anchors for access_denied_message and expose_hostname config options (cherry picked from commit 39f215f) --------- Co-authored-by: Ankit Chaurasia <8670962+sunank200@users.noreply.github.com>
Part of: #49896
This is still needed by the fab provider. Just confirming how things articulate between the provider / core dependency (provider requirements) on a minimal example, before moving on with other webserver config params.