-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Remove FAB db manager as an external_db_managers default
#48070
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
Remove FAB db manager as an external_db_managers default
#48070
Conversation
vincbeck
left a comment
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.
I am wondering if the config is the right option. Is it something that auth managers should set? I do not see a scenario where a user use FAB auth manager but not FABDBManager and vice versa. Should not we have a method in the auth manager interface like get_db_manager that FAB auth manager overrides?
|
We could refactor it to expose it from auth managers, that does make sense. But this should be done to simply the auth manager use case, not that auth managers are the only use case for db managers :) Would you oppose doing that in a follow up? |
|
@ephraimbuddy looks like we have some core/fab migration mixing going on. Is that something you could take a stab at? |
Yep I can do it as a follow-up |
Sure. Looking |
ca056a7 to
e99a2d7
Compare
|
7d8ac3a to
f9068ae
Compare
airflow-core/src/airflow/migrations/versions/0028_3_0_0_drop_ab_user_id_foreign_key.py
Outdated
Show resolved
Hide resolved
bf25391 to
65b52d0
Compare
96c43c7 to
0c95b2a
Compare
Now that the FAB auth manager isn't the default auth manager, it doesn't makes sense to have the FAB db manager as a default in `external_db_managers`.
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
496a290 to
fccfc7e
Compare
) * Remove FAB db manager as an `external_db_managers` default Now that the FAB auth manager isn't the default auth manager, it doesn't makes sense to have the FAB db manager as a default in `external_db_managers`. * Update migration to work when FAB is not among configured DB managers * Sync perms only when using FABAuthManager * Run tests with or without the fabauthmanager * Fix tests * Auth managers can now provide their own db manager! * Update airflow-core/src/airflow/dag_processing/collection.py Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> * Make 'ab_user' table a hard requirement when user is downgrading below 3.0.0 * Apply suggestions from code review * Fix whitespace in migration test * use env var for migration test * properly handle downgrade check * fixup! properly handle downgrade check * Update .pre-commit-config.yaml * apply suggestions from code review --------- Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
) * Remove FAB db manager as an `external_db_managers` default Now that the FAB auth manager isn't the default auth manager, it doesn't makes sense to have the FAB db manager as a default in `external_db_managers`. * Update migration to work when FAB is not among configured DB managers * Sync perms only when using FABAuthManager * Run tests with or without the fabauthmanager * Fix tests * Auth managers can now provide their own db manager! * Update airflow-core/src/airflow/dag_processing/collection.py Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> * Make 'ab_user' table a hard requirement when user is downgrading below 3.0.0 * Apply suggestions from code review * Fix whitespace in migration test * use env var for migration test * properly handle downgrade check * fixup! properly handle downgrade check * Update .pre-commit-config.yaml * apply suggestions from code review --------- Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
) * Remove FAB db manager as an `external_db_managers` default Now that the FAB auth manager isn't the default auth manager, it doesn't makes sense to have the FAB db manager as a default in `external_db_managers`. * Update migration to work when FAB is not among configured DB managers * Sync perms only when using FABAuthManager * Run tests with or without the fabauthmanager * Fix tests * Auth managers can now provide their own db manager! * Update airflow-core/src/airflow/dag_processing/collection.py Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> * Make 'ab_user' table a hard requirement when user is downgrading below 3.0.0 * Apply suggestions from code review * Fix whitespace in migration test * use env var for migration test * properly handle downgrade check * fixup! properly handle downgrade check * Update .pre-commit-config.yaml * apply suggestions from code review --------- Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
Now that the FAB auth manager isn't the default auth manager, it doesn't makes sense to have the FAB db manager as a default in
external_db_managers.