Skip to content

Surface provider triggers in the operators and hooks reference - #71975

Open
subhramit wants to merge 1 commit into
apache:mainfrom
subhramit:provider-triggers-in-docs
Open

Surface provider triggers in the operators and hooks reference#71975
subhramit wants to merge 1 commit into
apache:mainfrom
subhramit:provider-triggers-in-docs

Conversation

@subhramit

@subhramit subhramit commented Aug 22, 2026

Copy link
Copy Markdown

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 triggers entries 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?
  • Yes (please specify the tool below)

Generated-by: GPT-5.4 following the guidelines
All code changes (and also this description) were manually touched up and reviewed by me.

Signed-off-by: subhramit <subhramit.bb@live.in>
@boring-cyborg

boring-cyborg Bot commented Aug 22, 2026

Copy link
Copy Markdown

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
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack

@subhramit subhramit changed the title Surface triggers in provider docs reference Surface provider triggers in the operators and hooks reference Aug 22, 2026
@eladkal
eladkal requested a review from potiuk August 22, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Triggers to provider information

1 participant