This is an automated email from the ASF dual-hosted git repository.

vincbeck pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 14560e4d2a5 Clarify FAB and Auth documentation regarding 
external_db_managers (#69929)
14560e4d2a5 is described below

commit 14560e4d2a590555b76babf5ace52ec2403ddd19
Author: Stephan <[email protected]>
AuthorDate: Wed Jul 15 18:39:21 2026 +0200

    Clarify FAB and Auth documentation regarding external_db_managers (#69929)
    
    This PR clarifies the related documentation by:
    
    - Replacing the incorrectly used [core] external_db_managers section with 
[database] external_db_managers.
    - Rewording misleading statements that suggested DB managers are added to 
the external_db_managers configuration, when they are actually loaded 
automatically at runtime.
---
 airflow-core/docs/core-concepts/auth-manager/index.rst | 4 ++--
 providers/fab/docs/upgrading.rst                       | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/airflow-core/docs/core-concepts/auth-manager/index.rst 
b/airflow-core/docs/core-concepts/auth-manager/index.rst
index 49d761b174b..b821fbfa135 100644
--- a/airflow-core/docs/core-concepts/auth-manager/index.rst
+++ b/airflow-core/docs/core-concepts/auth-manager/index.rst
@@ -257,8 +257,8 @@ Other optional methods
   Override this method if you need to make any action (e.g. create resources, 
API call) that the auth manager needs.
 * ``get_extra_menu_items``: Provide additional links to be added to the menu 
in the UI.
 * ``get_db_manager``: If your auth manager requires one or several database 
managers (see :class:`~airflow.utils.db_manager.BaseDBManager`),
-  their class paths need to be returned as part of this method. By doing so, 
they will be automatically added to the
-  config ``[database] external_db_managers``.
+  their class paths need to be returned as part of this method. By doing so, 
Airflow automatically loads the
+  respective database managers.
 
 
 Additional Caveats
diff --git a/providers/fab/docs/upgrading.rst b/providers/fab/docs/upgrading.rst
index 3e861fb1a7e..4a7bf4cfab5 100644
--- a/providers/fab/docs/upgrading.rst
+++ b/providers/fab/docs/upgrading.rst
@@ -25,12 +25,12 @@ Why you need to upgrade
 The FAB provider is a separate package from Airflow and it is released 
independently. Starting from version 1.3.0, FAB
 can now run its own migrations if you are on Airflow 3. Newer FAB versions can 
contain database migrations, so you
 must run ``airflow fab-db migrate`` to migrate your database with the schema 
changes in the FAB version you are
-upgrading to. If ``FABDBManager`` is included in the ``[core] 
external_db_managers`` configuration, the migrations will
+upgrading to. If ``FABDBManager`` is included in the ``[database] 
external_db_managers`` configuration, the migrations will
 be run automatically as part of the ``airflow db migrate`` command.
 
 .. note::
-    If FAB auth manager is configured as auth manager in your environment, 
``FABDBManager`` is automatically added in the
-    ``[core] external_db_managers`` configuration.
+    If the FAB auth manager is configured as ``[core] auth_manager`` in your 
environment, Airflow automatically loads
+    ``FABDBManager`` and runs its migrations as part of the ``airflow db 
migrate`` command.
 
 How to upgrade
 ==============

Reply via email to