Authoring your provider

Now that we’ve got our project layout created, it’s time to start modifying our packaging files and code to ensure that our provider package integrates well with Airflow.

General design considerations

Due to the way Airflow interacts with the code it executes, there are a few important things to keep in mind when authoring your provider.

Code should be able to run without access to the internet. The Airflow Scheduler parses DAGs on a regular cadence. When that parsing occurs, anything in the `__init__` method of a class will be executed, including calls to third-party APIs and services.

Initialization methods should not call functions that only return valid objects during task execution. If this is violated, you will encounter import errors when attempting to use a provider in a DAG. You should instead use Jinja templating and macros within your DAG to manage these kinds of configurations.

All operators require an execute method...