This is an automated email from the ASF dual-hosted git repository. kaxilnaik pushed a commit to branch v3-0-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit fa72d055b80a0ad77ceea0f96e2c1789e48117e1 Author: Vincent <[email protected]> AuthorDate: Fri Apr 18 08:03:23 2025 -0400 Add note in FAB migration doc (#49423) (cherry picked from commit f65eeb05f48d9ad67cdbbeb81a5db085c519aaba) --- airflow-core/src/airflow/config_templates/config.yml | 3 ++- providers/fab/docs/upgrading.rst | 4 ++++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/airflow-core/src/airflow/config_templates/config.yml b/airflow-core/src/airflow/config_templates/config.yml index 1b71e5ae019..61641618393 100644 --- a/airflow-core/src/airflow/config_templates/config.yml +++ b/airflow-core/src/airflow/config_templates/config.yml @@ -697,7 +697,8 @@ database: external_db_managers: description: | List of DB managers to use to migrate external tables in airflow database. The managers must inherit - from BaseDBManager + from BaseDBManager. If ``FabAuthManager`` is configured in the environment, + ``airflow.providers.fab.auth_manager.models.db.FABDBManager`` is automatically added. version_added: 3.0.0 type: string example: "airflow.providers.fab.auth_manager.models.db.FABDBManager" diff --git a/providers/fab/docs/upgrading.rst b/providers/fab/docs/upgrading.rst index 28c046d9c03..3e861fb1a7e 100644 --- a/providers/fab/docs/upgrading.rst +++ b/providers/fab/docs/upgrading.rst @@ -28,6 +28,10 @@ must run ``airflow fab-db migrate`` to migrate your database with the schema cha upgrading to. If ``FABDBManager`` is included in the ``[core] 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. + How to upgrade ============== To upgrade the FAB provider, you need to install the new version of the package. You can do this using ``pip``.
