Add more provider module categories to the provider page#70190
Open
Lee-W wants to merge 4 commits into
Open
Conversation
boring-cyborg
Bot
added
area:dev-tools
area:registry
backport-to-v3-3-test
Lee-W
marked this pull request as ready for review
July 21, 2026 14:11
Lee-W
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl,
kaxil,
potiuk and
vatsrahul1001
as code owners
July 21, 2026 14:11
potiuk
approved these changes
Jul 21, 2026
phanikumv
reviewed
Jul 21, 2026
kaxil
reviewed
Jul 21, 2026
kaxil
reviewed
Jul 21, 2026
Lee-W
force-pushed
the
add-more-registry-module-categories
branch
3 times, most recently
from
July 22, 2026 05:43
1bae222 to
e0be06b
Compare
phanikumv
reviewed
Jul 22, 2026
Lee-W
force-pushed
the
add-more-registry-module-categories
branch
2 times, most recently
from
July 23, 2026 07:10
a1ffe7e to
4ab25a3
Compare
Lee-W
force-pushed
the
add-more-registry-module-categories
branch
from
July 23, 2026 09:46
29c43b0 to
00935eb
Compare
extract_versions.py hardcoded a 4-entry FQCN_SECTIONS map, so backfilled (older) provider version pages only showed notifications, secrets backends, logging, and executors. The newer categories added for the provider page (extra links, queues, auth managers, db managers) only showed up on the latest version page, which used a separate code path already wired to all categories. extract_versions.py now derives its category list from CLASS_LEVEL_SECTIONS instead of duplicating it, and the category overrides that used to live only in extract_parameters.py move to a shared CLASS_LEVEL_CATEGORY_OVERRIDES constant so both scripts stay in sync going forward.
"Queues" was easy to confuse with the "queue" argument on BaseOperator, which is unrelated to message queue providers.
Class-level sections, plugins, dialects, and task-decorators each repeated the same split/import/getattr logic for resolving a dotted class or function path, making it easy for the failure handling in one copy to drift from the others. Also widens _get_first_docstring_line's parameter type to object, since it only ever reads __doc__ and doesn't require an actual class -- mypy caught the mismatch once the new helper's return type stopped inferring as Any at the task-decorators call site.
Lee-W
force-pushed
the
add-more-registry-module-categories
branch
from
July 23, 2026 10:04
00935eb to
3f6d9dc
Compare
Member
Author
|
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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
Follow up of #70122. Extra links, queues, plugins, auth managers, DB managers, and dialects were not browsable in the registry
What
Add extra links, queues, plugins, auth managers, DB managers, and dialects. Each of them now gets it own category tab. The row now sorted by module count and tail collapses into a "More" menu so the page won't be too messy
Was generative AI tooling used to co-author this PR?
{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.