Exactly the kind of thing Registry will bubble up on various inconsistencies.
Our markers for Connection types were inconsistent too, which have been fixed since then. On Tue, 24 Mar 2026 at 00:42, Jarek Potiuk <[email protected]> wrote: > > I suspect we actually have more. I looked through it on Friday and > noticed several Amazon items missing which I have since added to the > provider yaml. It makes me wonder how many are missing in other packages. > > WE we have a prek hook that checked those for consistency.. But it did not > have notifiers and executors (when we added those we have not added > validation) > > PR here: https://github.com/apache/airflow/pull/64127 > > > ┌───────────┬────────────┬───────────────────────────────────────────┐ > │ Type │ Discovered │ Status │ > ├───────────┼────────────┼───────────────────────────────────────────┤ > │ Operators │ 936 │ All OK │ > ├───────────┼────────────┼───────────────────────────────────────────┤ > │ Hooks │ 307 │ All OK │ > ├───────────┼────────────┼───────────────────────────────────────────┤ > │ Triggers │ 155 │ All OK │ > ├───────────┼────────────┼───────────────────────────────────────────┤ > │ Sensors │ 152 │ All OK │ > ├───────────┼────────────┼───────────────────────────────────────────┤ > │ Notifiers │ 13 │ All OK (aliases properly deduped) │ > ├───────────┼────────────┼───────────────────────────────────────────┤ > │ Executors │ 8 │ 7 OK, 1 MISSING (LocalKubernetesExecutor) │ > ├───────────┼────────────┼───────────────────────────────────────────┤ > │ Total │ 1,571 │ 1 error │ > └───────────┴────────────┴───────────────────────────────────────────┘ > > I've added the LocalKubernetesExecutor since. > > J, > > > On Mon, Mar 23, 2026 at 8:57 PM Ferruzzi, Dennis <[email protected]> > wrote: > > > > I was playing around the registry and I noticed we have 848(!!!) > > operators! > > > > I suspect we actually have more. I looked through it on Friday and > > noticed several Amazon items missing which I have since added to the > > provider yaml. It makes me wonder how many are missing in other > packages. > > ________________________________ > > From: Amogh Desai <[email protected]> > > Sent: Sunday, March 22, 2026 10:51 PM > > To: [email protected] <[email protected]> > > Subject: RE: [EXT] [ANNOUNCE] Apache Airflow Registry — searchable > catalog > > of all providers and modules > > > > CAUTION: This email originated from outside of the organization. Do not > > click links or open attachments unless you can confirm the sender and > know > > the content is safe. > > > > > > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne > pouvez > > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain > que > > le contenu ne présente aucun risque. > > > > > > > > This is really amazing, Kaxil. > > > > I was playing around the registry and I noticed we have 848(!!!) > operators! > > Wow! > > > > Thanks & Regards, > > Amogh Desai > > > > > > On Fri, Mar 20, 2026 at 11:36 AM Shahar Epstein <[email protected]> > wrote: > > > > > Great work Kaxil! Well done :) > > > > > > > > > Shahar > > > > > > On Thu, Mar 19, 2026, 22:25 Kaxil Naik <[email protected]> wrote: > > > > > > > Hi everyone, > > > > > > > > We just launched the Apache Airflow Registry: > > > > > > > > https://airflow.apache.org/registry/ > > > > > > > > It's a searchable catalog of every official Airflow provider and > module > > > > — 98 providers, 1,602 modules (operators, hooks, sensors, triggers, > > > > transfers, secrets backends, executors, and more) covering 125+ > > > > integrations. Collectively these providers see 329M+ monthly PyPI > > > > downloads. > > > > > > > > Features: > > > > > > > > - Instant search (Cmd+K / Ctrl+K) across all providers and modules, > > > > with results grouped by type > > > > > > > > - Dedicated provider pages with install commands, version selector, > > > > extras, compatibility info, connection types, and full module > > listings > > > > > > > > - Connection builder — select a connection type, fill in the fields, > > > > and get the connection string in URI, JSON, or Env Var format > > > > > > > > - JSON API — all registry data is available as structured JSON. An > API > > > > Explorer lets you browse endpoints interactively. This makes the > > > > registry accessible to IDE extensions, AI coding assistants, and > > > > automation tools: > > > > https://airflow.apache.org/registry/api-explorer/ > > > > > > > > - Full dark/light theme support > > > > > > > > The registry lives at airflow.apache.org, is built from the > registry/ > > > > directory in the main Airflow repo [1], and updates automatically > when > > > > new provider versions are published to PyPI. > > > > > > > > Thanks to Astronomer for building and maintaining the Astronomer > > > > Registry for years — it proved the value of a searchable provider > > > > catalog and directly shaped this community-owned version. > > > > > > > > What's next: > > > > - Third-party provider support (community-built providers alongside > > > > official ones) > > > > - Richer module pages with full parameter docs and usage examples > > > > > > > > Blog post with screenshots and details: > > > > https://airflow.apache.org/blog/airflow-registry/ > > > > > > > > Feedback, bug reports, and feature requests welcome on GitHub [2] or > > > > on this list. > > > > > > > > [1] https://github.com/apache/airflow/tree/main/registry > > > > [2] https://github.com/apache/airflow/issues > > > > > > > > Regards, > > > > Kaxil > > > > > > > > > >
