Uh oh!
There was an error while loading. Please reload this page.
Resolve nested provider paths for conn-fields check from the real directory tree - #70261
Merged
Lee-W merged 1 commit intoJul 24, 2026
Conversation
Lee-Wforce-pushed
the
resolve-nested-provider-paths-from-the-real-directory-tree
branch
from
July 23, 2026 07:03
fdde0d6 to
8e476faCompareLee-W
marked this pull request as ready for review
July 23, 2026 07:06
Lee-W
requested review from
amoghrajesh, ashb, bugraoz93, gopidesupavan, jason810496, jscheffl and potiuk
as code ownersJuly 23, 2026 07:06
1 task
Lee-Wforce-pushed
the
resolve-nested-provider-paths-from-the-real-directory-tree
branch
from
July 23, 2026 08:33
8e476fa to
54d0e6dCompareLee-W
requested review from
choo121600, ephraimbuddy, jedcunningham and vatsrahul1001
as code ownersJuly 23, 2026 08:33
gopidesupavan
approved these changes
Jul 23, 2026
amoghrajesh
approved these changes
Jul 23, 2026
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Lee-Wforce-pushed
the
resolve-nested-provider-paths-from-the-real-directory-tree
branch
from
July 23, 2026 09:58
54d0e6d to
6066ad7Compare…ectory tree The conn-fields prek hook guessed how many path segments made up a provider package name from a hardcoded list of known namespace prefixes, so it kept crashing on newly nested providers (e.g. IBM MQ) until someone manually patched the list. Walking the actual directory tree to find each provider's provider.yaml makes it work for any current or future nested provider automatically.
Lee-Wforce-pushed
the
resolve-nested-provider-paths-from-the-real-directory-tree
branch
from
July 23, 2026 10:09
6066ad7 to
cee89ccCompareUh oh!
There was an error while loading. Please reload this page.
Lee-W
deleted the
resolve-nested-provider-paths-from-the-real-directory-tree
branch
July 24, 2026 07:48
Contributor
Backport failed to create: v3-3-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 030efa6 v3-3-testThis should apply the commit to the v3-3-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
1 task
dabla pushed a commit
to dabla/airflow
that referenced
this pull request
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
#70224 (comment)
The conn-fields prek hook guessed how many path segments made up a provider package name from a hardcoded list of known namespace prefixes, so it kept crashing on newly nested providers (e.g. IBM MQ) until someone manually patched the list.
What
Walking the actual directory tree to find each provider's provider.yaml makes it work for any current or future nested provider automatically.
Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.