dheerajturaga opened a new pull request, #75167: URL: https://github.com/apache/airflow/pull/75167
### Stack Stacks on #75166. Stack index: 19 of 20. Its base is the branch of #75166, so the diff shows only this layer's commit, "AIP-125: Document inbound webhooks". ### Status Draft. [AIP-125 (Inbound Webhooks)](https://lists.apache.org/thread/p3dpnor4zwko8tldpncj6ftj1bpp18q7) is under discussion on dev@ and not yet voted; this stack is its proof of concept so that voters can run it, and nothing should merge before the vote. The feature is opt-in and experimental; these docs describe it as stack PR 18 exposes it, and are meant to land with that PR, which merges last. ### Why Inbound webhooks ship opt-in and experimental, so Deployment Managers need to know how to run the separate webhooks process safely, Dag authors how topic names and runs behave, and provider authors what a source type must and must not do. The public interface page now lists the source type interface, and the db clean docs say why `inbound_delivery` rows age by `retain_until`. ### What to look at - `administration-and-deployment/webhooks.rst`: setup, the process, configuration, outcomes, stored payloads, retention, metrics, least privilege, turning webhooks off, and migrating from `airflow-provider-inbound-webhooks`. - `authoring-and-scheduling/webhook-topics.rst`: topic names, the ASCII and URI rules, how to check that an event came from a webhook, runs, and two examples. - `providers-summary-docs/core-extensions/webhook-sources.rst`: the contract for provider authors. - `public-airflow-interface.rst`: `airflow.webhooks.base` and `airflow.webhooks.naming` as public, experimental interfaces. ### Testing - `breeze build-docs`, spelling included, is clean for apache-airflow, apache-airflow-providers, the standard, GitHub and FAB providers, task-sdk and airflow-ctl; rerun for apache-airflow, standard and GitHub after the last fixes. ### Newsfragment `airflow-core/newsfragments/0.significant.rst` covers the opt-in feature, the reserved `/webhooks` prefix, the new table, and notes for users of the proof-of-concept package. It is the only newsfragment in the stack. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5.5) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
