Frequently Asked Questions
What is an Apache Airflow Provider?
An Airflow Provider is a Python package that allows users to interface with third-party tools and APIs using a set of supported abstractions. Each package is applied to a specific service and contains all relevant modules for a service.
What is a Module?
A module on the Astronomer Registry is an entity that can be imported from a provider package for use in either an Airflow DAG or an
airflow.cfgfile. There are various types of modules, including hooks, operators, sensors, and transfers.
How do I build an Airflow Provider for my tool?
We're open to partnering with anyone who wants to build a stronger integration between Airflow and their tool via a supported first-class integration. To kickstart the process, review our Sample Provider Repo and get in touch with our team to join our beta program for building and delivering Partner Providers.
Can I build a personal provider for my custom operators?
We welcome submissions from anyone in the community who has built custom modules and wants to give other Airflow users the ability to try them out. To build your modules into a provider package that can be published on the Astronomer Registry, follow the steps in our Sample Provider Repo and get in touch with our team to have your package reviewed and published as a "community" provider.
How often is the data on the Registry updated?
The data that's displayed in the Registry, including download count, version, and publish date, is updated every night by an Airflow DAG.