Surface provider triggers in the operators and hooks reference - #71975
Open
subhramit wants to merge 1 commit into
Open
Surface provider triggers in the operators and hooks reference#71975subhramit wants to merge 1 commit into
subhramit wants to merge 1 commit into
Conversation
Signed-off-by: subhramit <subhramit.bb@live.in>
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
|
7 tasks
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
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.
Closes #29918
This completes the remaining part of the issue by surfacing provider triggers in the generated operators and hook reference.
The Sphinx extension now reads
triggersentries from provider metadata and renders them in the generated providers summary docs. It also includes integrations that expose triggers even when they do not define operators, hooks, or sensors.Have added a unit test covering the trigger-only integration case.
Was generative AI tooling used to co-author this PR?
Generated-by: GPT-5.4 following the guidelines
All code changes (and also this description) were manually touched up and reviewed by me.