fix: FAB get_application_builder should use create_metadata_engine hook - #71673
bujjibabukatta wants to merge 4 commits into
Conversation
|
Hello @bujjibabukatta - thank you for your contributions to Apache Airflow! The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 16 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are. What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack. Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst. Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting |
Summary
Fixes createUserJob (and other FAB CLI/API user & role management commands) failing to
connect to the database when a custom
create_metadata_engineis defined inairflow_local_settings.py(e.g. for IAM/token-based DB auth).Root cause
get_application_builder()created its own Flask-SQLAlchemy engine directly fromSQLALCHEMY_DATABASE_URI, bypassingairflow.settings.create_metadata_engine. So anycustom engine-creation logic in
airflow_local_settings.pywas silently ignored forthis engine, even though it works correctly for Airflow's main metadata engine.
Fix
Added an
_AirflowFlaskSQLAlchemysubclass that overrides_make_engineto build theengine via
airflow.settings.create_metadata_engine, so it now honors the sameoverride as the rest of Airflow.
Closes: #71664
Was generative AI tooling used ?
Generated-by: Claude following the guidelines