> Just saw this @Ferruzzi, Dennis<mailto:[email protected]> : > https://github.com/apache/airflow/pull/64009 -- Nice
I only caught it because of your project, so back at you π - βferruzzi ________________________________ From: Jarek Potiuk <[email protected]> Sent: Tuesday, March 24, 2026 2:52 AM To: [email protected] <[email protected]> Cc: Ferruzzi, Dennis <[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. Just saw this @Ferruzzi, Dennis <[email protected]> : https://github.com/apache/airflow/pull/64009 -- Nice > Yep. This is what inspired me to make sure it won't happen again ;) 2 claude prompts away we had the PR :) On Tue, Mar 24, 2026 at 9:43β―AM Kaxil Naik <[email protected]<mailto:[email protected]>> wrote: Just saw this @Ferruzzi, Dennis <[email protected]> : https://github.com/apache/airflow/pull/64009 -- Nice On Tue, 24 Mar 2026 at 08:39, Jarek Potiuk <[email protected]<mailto:[email protected]>> wrote: > > LocalK8s Executor we shouldnβt imo since we now have hybrid Exec/ > I considered it, yes, but I looked it up and we also have > CeleryKubernetesExecutor (which is available for providers to use in > Airflow 2). They raise exception when you use them in Airflow 3. > > I think it's still fine to show them until we support Airflow 2 (maybe we > should add a description to clearly state that they are Airflow 2 - only). > I think we should only drop those when we drop Airflow 2 support - > yes HybridExecutors were there since 2.10 - but I can't remember if there > were any breaking changes or serious flaws. As far as I remember we made > Hybrid Executors default (and the only) version only in Airflow 3? > > I think there is a good reason we still keep them and we want to > communicate about them until Airflow 2 support is dropped. We could also > drop them earlier - but IMHO they should be dropped from code and from > .yaml at the same time. > > J. > > > On Tue, Mar 24, 2026 at 9:22β―AM Kaxil Naik > <[email protected]<mailto:[email protected]>> wrote: > > > LocalK8s Executor we shouldnβt imo since we now have hybrid Exec > > > > On Tue, 24 Mar 2026 at 08:21, Kaxil Naik > > <[email protected]<mailto:[email protected]>> wrote: > > > > > 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]<mailto:[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]<mailto:[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]<mailto:[email protected]>> > > >> > Sent: Sunday, March 22, 2026 10:51 PM > > >> > To: [email protected]<mailto:[email protected]> > > >> > <[email protected]<mailto:[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]<mailto:[email protected]>> > > >> wrote: > > >> > > > >> > > Great work Kaxil! Well done :) > > >> > > > > >> > > > > >> > > Shahar > > >> > > > > >> > > On Thu, Mar 19, 2026, 22:25 Kaxil Naik > > >> > > <[email protected]<mailto:[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<http://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 > > >> > > > > > >> > > > > >> > > > >> > > > > > >
