This is an automated email from the ASF dual-hosted git repository.
turaga 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 182161b4e8f docs: edge3 db-manager is auto loaded by provider manager
(#62550)
182161b4e8f is described below
commit 182161b4e8f5ff02667745354a5334da7c364577
Author: Dheeraj Turaga <[email protected]>
AuthorDate: Mon Mar 2 20:07:36 2026 -0600
docs: edge3 db-manager is auto loaded by provider manager (#62550)
* docs: edge3 db-manager is auto loaded by provider manager
* docs: edge3 external_db_managers still required for Airflow < 3.2
Auto-registration of EdgeDBManager via ProvidersManager is only
available from Airflow 3.2 onwards. Restore the manual
external_db_managers configuration instructions for earlier versions.
---
providers/edge3/docs/deployment.rst | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/providers/edge3/docs/deployment.rst
b/providers/edge3/docs/deployment.rst
index caa6bc8ad47..7076b823923 100644
--- a/providers/edge3/docs/deployment.rst
+++ b/providers/edge3/docs/deployment.rst
@@ -66,9 +66,13 @@ Minimum Airflow configuration settings for the Edge Worker
to make it running is
- ``api_url``: Must be set to the URL which exposes the api endpoint as it
is reachable from the
worker. Typically this looks like
``https://your-hostname-and-port/edge_worker/v1/rpcapi``.
-The following setting is required on the **central Airflow instance** (not the
edge worker node)
-so that edge3 database tables (``edge_worker``, ``edge_job``, ``edge_logs``)
are created and
-migrated when running ``airflow db migrate``:
+**Airflow 3.2 and newer:** Once the provider is installed on the **central
Airflow instance**,
+the ``EdgeDBManager`` is automatically registered via the provider's built-in
``db-managers``
+entry. Airflow's ``ProvidersManager`` discovers it at startup — no manual
configuration is needed.
+
+**Airflow versions earlier than 3.2:** You must explicitly register the
``EdgeDBManager`` on the
+**central Airflow instance** so that edge3 database tables (``edge_worker``,
``edge_job``,
+``edge_logs``) are created and migrated when running ``airflow db migrate``:
- Section ``[database]``
@@ -94,8 +98,8 @@ migrated when running ``airflow db migrate``:
[database]
external_db_managers =
airflow.providers.fab.auth_manager.models.db.FABDBManager,airflow.providers.edge3.models.db.EdgeDBManager
-After configuring ``external_db_managers``, run the following on the central
Airflow instance
-to apply the edge3 schema migrations:
+To create or migrate the edge3 database tables (``edge_worker``, ``edge_job``,
``edge_logs``),
+run on the central Airflow instance:
.. code-block:: bash
