Skip to content

Conversation

@jedcunningham
Copy link
Member

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.

Copy link
Contributor

@vincbeck vincbeck left a 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?

@jedcunningham
Copy link
Member Author

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?

@jedcunningham
Copy link
Member Author

@ephraimbuddy looks like we have some core/fab migration mixing going on. Is that something you could take a stab at?

@vincbeck
Copy link
Contributor

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?

Yep I can do it as a follow-up

@ephraimbuddy
Copy link
Contributor

@ephraimbuddy looks like we have some core/fab migration mixing going on. Is that something you could take a stab at?

Sure. Looking

@vincbeck
Copy link
Contributor

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?

#48196

@ephraimbuddy ephraimbuddy force-pushed the remove_fab_db_manager_default branch 2 times, most recently from 7d8ac3a to f9068ae Compare March 25, 2025 12:12
@ephraimbuddy ephraimbuddy force-pushed the remove_fab_db_manager_default branch 2 times, most recently from bf25391 to 65b52d0 Compare March 25, 2025 21:06
@ephraimbuddy ephraimbuddy force-pushed the remove_fab_db_manager_default branch 2 times, most recently from 96c43c7 to 0c95b2a Compare March 26, 2025 15:16
@ephraimbuddy ephraimbuddy requested a review from vincbeck March 27, 2025 08:08
@ephraimbuddy ephraimbuddy force-pushed the remove_fab_db_manager_default branch from 496a290 to fccfc7e Compare March 28, 2025 21:02
@ephraimbuddy ephraimbuddy requested a review from vincbeck March 28, 2025 21:02
@vincbeck vincbeck merged commit 6f26a38 into apache:main Apr 2, 2025
7 checks passed
nailo2c pushed a commit to nailo2c/airflow that referenced this pull request Apr 4, 2025
)

* 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>
@ephraimbuddy ephraimbuddy deleted the remove_fab_db_manager_default branch April 6, 2025 11:26
diogotrodrigues pushed a commit to diogotrodrigues/airflow that referenced this pull request Apr 6, 2025
)

* 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>
simonprydden pushed a commit to simonprydden/airflow that referenced this pull request Apr 8, 2025
)

* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants