%global _empty_manifest_terminate_build 0
Name: python-apache-airflow
Version: 2.5.3
Release: 1
Summary: Programmatically author, schedule and monitor data pipelines
License: Apache License 2.0
URL: https://airflow.apache.org/
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/56/96/742af5b44ff769d83019b73e1dce010c28f4deef542e72e09869a9dc17ab/apache-airflow-2.5.3.tar.gz
BuildArch: noarch
Requires: python3-alembic
Requires: python3-argcomplete
Requires: python3-attrs
Requires: python3-blinker
Requires: python3-cattrs
Requires: python3-colorlog
Requires: python3-configupdater
Requires: python3-connexion[flask]
Requires: python3-cron-descriptor
Requires: python3-croniter
Requires: python3-cryptography
Requires: python3-deprecated
Requires: python3-dill
Requires: python3-flask
Requires: python3-flask-appbuilder
Requires: python3-flask-caching
Requires: python3-flask-login
Requires: python3-flask-session
Requires: python3-flask-wtf
Requires: python3-graphviz
Requires: python3-gunicorn
Requires: python3-httpx
Requires: python3-itsdangerous
Requires: python3-jinja2
Requires: python3-jsonschema
Requires: python3-lazy-object-proxy
Requires: python3-linkify-it-py
Requires: python3-lockfile
Requires: python3-markdown
Requires: python3-markdown-it-py
Requires: python3-markupsafe
Requires: python3-marshmallow-oneofschema
Requires: python3-mdit-py-plugins
Requires: python3-packaging
Requires: python3-pathspec
Requires: python3-pendulum
Requires: python3-pluggy
Requires: python3-psutil
Requires: python3-pygments
Requires: python3-pyjwt
Requires: python3-daemon
Requires: python3-dateutil
Requires: python3-nvd3
Requires: python3-slugify
Requires: python3-rfc3339-validator
Requires: python3-rich
Requires: python3-setproctitle
Requires: python3-sqlalchemy
Requires: python3-sqlalchemy-jsonfield
Requires: python3-tabulate
Requires: python3-tenacity
Requires: python3-termcolor
Requires: python3-typing-extensions
Requires: python3-unicodecsv
Requires: python3-werkzeug
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-apache-airflow-providers-ftp
Requires: python3-apache-airflow-providers-http
Requires: python3-apache-airflow-providers-imap
Requires: python3-apache-airflow-providers-sqlite
Requires: python3-importlib-metadata
Requires: python3-importlib-resources
Requires: python3-cached-property
Requires: python3-apache-airflow-providers-airbyte
Requires: python3-apache-airflow-providers-alibaba
Requires: python3-JIRA
Requires: python3-PyOpenSSL
Requires: python3-adal
Requires: python3-aiohttp
Requires: python3-amqp
Requires: python3-analytics-python
Requires: python3-apache-airflow
Requires: python3-apache-airflow
Requires: python3-apache-beam
Requires: python3-arrow
Requires: python3-asana
Requires: python3-asgiref
Requires: python3-atlasclient
Requires: python3-authlib
Requires: python3-azure-batch
Requires: python3-azure-cosmos
Requires: python3-azure-datalake-store
Requires: python3-azure-identity
Requires: python3-azure-keyvault-secrets
Requires: python3-azure-kusto-data
Requires: python3-azure-mgmt-containerinstance
Requires: python3-azure-mgmt-datafactory
Requires: python3-azure-mgmt-datalake-store
Requires: python3-azure-mgmt-resource
Requires: python3-azure-storage-blob
Requires: python3-azure-storage-common
Requires: python3-azure-storage-file
Requires: python3-azure-synapse-spark
Requires: python3-bcrypt
Requires: python3-blinker
Requires: python3-boto3
Requires: python3-cassandra-driver
Requires: python3-celery
Requires: python3-cgroupspy
Requires: python3-cloudant
Requires: python3-cloudpickle
Requires: python3-cryptography
Requires: python3-dask
Requires: python3-databricks-sql-connector
Requires: python3-datadog
Requires: python3-distributed
Requires: python3-dnspython
Requires: python3-docker
Requires: python3-elasticsearch-dbapi
Requires: python3-elasticsearch-dsl
Requires: python3-elasticsearch
Requires: python3-eventlet
Requires: python3-facebook-business
Requires: python3-flask-appbuilder[oauth]
Requires: python3-flask-bcrypt
Requires: python3-flower
Requires: python3-gcloud-aio-bigquery
Requires: python3-gcloud-aio-storage
Requires: python3-gcloud-aio-auth
Requires: python3-gevent
Requires: python3-google-ads
Requires: python3-google-api-core
Requires: python3-google-api-python-client
Requires: python3-google-auth-httplib2
Requires: python3-google-auth
Requires: python3-google-auth
Requires: python3-google-cloud-aiplatform
Requires: python3-google-cloud-automl
Requires: python3-google-cloud-bigquery-datatransfer
Requires: python3-google-cloud-bigtable
Requires: python3-google-cloud-build
Requires: python3-google-cloud-compute
Requires: python3-google-cloud-container
Requires: python3-google-cloud-datacatalog
Requires: python3-google-cloud-dataform
Requires: python3-google-cloud-dataplex
Requires: python3-google-cloud-dataproc-metastore
Requires: python3-google-cloud-dataproc
Requires: python3-google-cloud-dlp
Requires: python3-google-cloud-kms
Requires: python3-google-cloud-language
Requires: python3-google-cloud-logging
Requires: python3-google-cloud-memcache
Requires: python3-google-cloud-monitoring
Requires: python3-google-cloud-orchestration-airflow
Requires: python3-google-cloud-os-login
Requires: python3-google-cloud-pubsub
Requires: python3-google-cloud-redis
Requires: python3-google-cloud-secret-manager
Requires: python3-google-cloud-spanner
Requires: python3-google-cloud-speech
Requires: python3-google-cloud-storage
Requires: python3-google-cloud-tasks
Requires: python3-google-cloud-texttospeech
Requires: python3-google-cloud-translate
Requires: python3-google-cloud-videointelligence
Requires: python3-google-cloud-vision
Requires: python3-google-cloud-workflows
Requires: python3-greenlet
Requires: python3-grpcio-gcp
Requires: python3-grpcio
Requires: python3-hdfs[avro,dataframe,kerberos]
Requires: python3-hmsclient
Requires: python3-httpx
Requires: python3-hvac
Requires: python3-influxdb-client
Requires: python3-jaydebeapi
Requires: python3-json-merge-patch
Requires: python3-jsonpath-ng
Requires: python3-kubernetes
Requires: python3-kylinpy
Requires: python3-ldap3
Requires: python3-looker-sdk
Requires: python3-mypy-boto3-appflow
Requires: python3-mypy-boto3-rds
Requires: python3-mypy-boto3-redshift-data
Requires: python3-neo4j
Requires: python3-opsgenie-sdk
Requires: python3-oracledb
Requires: python3-oss2
Requires: python3-pandas-gbq
Requires: python3-pandas
Requires: python3-papermill[all]
Requires: python3-paramiko
Requires: python3-pdpyras
Requires: python3-pinotdb
Requires: python3-plyvel
Requires: python3-presto-python-client
Requires: python3-proto-plus
Requires: python3-protobuf
Requires: python3-psycopg2
Requires: python3-pydruid
Requires: python3-pyexasol
Requires: python3-pygithub
Requires: python3-pyhive[hive]
Requires: python3-pykerberos
Requires: python3-pymongo
Requires: python3-pymssql
Requires: python3-pyodbc
Requires: python3-pypsrp
Requires: python3-pyspark
Requires: python3-arango
Requires: python3-dotenv
Requires: python3-jenkins
Requires: python3-ldap
Requires: python3-telegram-bot
Requires: python3-pywinrm
Requires: python3-qds-sdk
Requires: python3-redis
Requires: python3-redshift-connector
Requires: python3-requests
Requires: python3-requests
Requires: python3-requests-kerberos
Requires: python3-requests-toolbelt
Requires: python3-scrapbook[all]
Requires: python3-sendgrid
Requires: python3-sentry-sdk
Requires: python3-simple-salesforce
Requires: python3-slack-sdk
Requires: python3-smbprotocol
Requires: python3-snakebite-py3
Requires: python3-snowflake-connector-python
Requires: python3-snowflake-sqlalchemy
Requires: python3-spython
Requires: python3-sqlalchemy-bigquery
Requires: python3-sqlalchemy-drill
Requires: python3-sqlalchemy-redshift
Requires: python3-sqlparse
Requires: python3-sshtunnel
Requires: python3-statsd
Requires: python3-tableauserverclient
Requires: python3-thrift
Requires: python3-thrift-sasl
Requires: python3-trino
Requires: python3-vertica-python
Requires: python3-virtualenv
Requires: python3-watchtower
Requires: python3-yandexcloud
Requires: python3-zenpy
Requires: python3-apache-airflow-providers-airbyte
Requires: python3-apache-airflow-providers-alibaba
Requires: python3-apache-airflow-providers-amazon
Requires: python3-apache-airflow-providers-apache-beam
Requires: python3-apache-airflow-providers-apache-cassandra
Requires: python3-apache-airflow-providers-apache-drill
Requires: python3-apache-airflow-providers-apache-druid
Requires: python3-apache-airflow-providers-apache-hdfs
Requires: python3-apache-airflow-providers-apache-hive
Requires: python3-apache-airflow-providers-apache-kylin
Requires: python3-apache-airflow-providers-apache-livy
Requires: python3-apache-airflow-providers-apache-pig
Requires: python3-apache-airflow-providers-apache-pinot
Requires: python3-apache-airflow-providers-apache-spark
Requires: python3-apache-airflow-providers-apache-sqoop
Requires: python3-apache-airflow-providers-arangodb
Requires: python3-apache-airflow-providers-asana
Requires: python3-apache-airflow-providers-atlassian-jira
Requires: python3-apache-airflow-providers-celery
Requires: python3-apache-airflow-providers-cloudant
Requires: python3-apache-airflow-providers-cncf-kubernetes
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-apache-airflow-providers-databricks
Requires: python3-apache-airflow-providers-datadog
Requires: python3-apache-airflow-providers-dbt-cloud
Requires: python3-apache-airflow-providers-dingding
Requires: python3-apache-airflow-providers-discord
Requires: python3-apache-airflow-providers-docker
Requires: python3-apache-airflow-providers-elasticsearch
Requires: python3-apache-airflow-providers-exasol
Requires: python3-apache-airflow-providers-facebook
Requires: python3-apache-airflow-providers-ftp
Requires: python3-apache-airflow-providers-github
Requires: python3-apache-airflow-providers-google
Requires: python3-apache-airflow-providers-grpc
Requires: python3-apache-airflow-providers-hashicorp
Requires: python3-apache-airflow-providers-http
Requires: python3-apache-airflow-providers-imap
Requires: python3-apache-airflow-providers-influxdb
Requires: python3-apache-airflow-providers-jdbc
Requires: python3-apache-airflow-providers-jenkins
Requires: python3-apache-airflow-providers-microsoft-azure
Requires: python3-apache-airflow-providers-microsoft-mssql
Requires: python3-apache-airflow-providers-microsoft-psrp
Requires: python3-apache-airflow-providers-microsoft-winrm
Requires: python3-apache-airflow-providers-mongo
Requires: python3-apache-airflow-providers-mysql
Requires: python3-apache-airflow-providers-neo4j
Requires: python3-apache-airflow-providers-odbc
Requires: python3-apache-airflow-providers-openfaas
Requires: python3-apache-airflow-providers-opsgenie
Requires: python3-apache-airflow-providers-oracle
Requires: python3-apache-airflow-providers-pagerduty
Requires: python3-apache-airflow-providers-papermill
Requires: python3-apache-airflow-providers-plexus
Requires: python3-apache-airflow-providers-postgres
Requires: python3-apache-airflow-providers-presto
Requires: python3-apache-airflow-providers-qubole
Requires: python3-apache-airflow-providers-redis
Requires: python3-apache-airflow-providers-salesforce
Requires: python3-apache-airflow-providers-samba
Requires: python3-apache-airflow-providers-segment
Requires: python3-apache-airflow-providers-sendgrid
Requires: python3-apache-airflow-providers-sftp
Requires: python3-apache-airflow-providers-singularity
Requires: python3-apache-airflow-providers-slack
Requires: python3-apache-airflow-providers-snowflake
Requires: python3-apache-airflow-providers-sqlite
Requires: python3-apache-airflow-providers-ssh
Requires: python3-apache-airflow-providers-tableau
Requires: python3-apache-airflow-providers-tabular
Requires: python3-apache-airflow-providers-telegram
Requires: python3-apache-airflow-providers-trino
Requires: python3-apache-airflow-providers-vertica
Requires: python3-apache-airflow-providers-yandex
Requires: python3-apache-airflow-providers-zendesk
Requires: python3-azure-servicebus
Requires: python3-mysql-connector-python
Requires: python3-mysqlclient
Requires: python3-sasl
Requires: python3-aiohttp
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-apache-airflow
Requires: python3-cassandra-driver
Requires: python3-cloudant
Requires: python3-databricks-sql-connector
Requires: python3-dnspython
Requires: python3-hdfs[avro,dataframe,kerberos]
Requires: python3-hmsclient
Requires: python3-influxdb-client
Requires: python3-neo4j
Requires: python3-pandas
Requires: python3-pinotdb
Requires: python3-presto-python-client
Requires: python3-psycopg2
Requires: python3-pydruid
Requires: python3-pyexasol
Requires: python3-pyhive[hive]
Requires: python3-pymongo
Requires: python3-pymssql
Requires: python3-arango
Requires: python3-requests
Requires: python3-requests
Requires: python3-snakebite-py3
Requires: python3-sqlalchemy-drill
Requires: python3-thrift
Requires: python3-trino
Requires: python3-vertica-python
Requires: python3-apache-airflow-providers-apache-cassandra
Requires: python3-apache-airflow-providers-apache-drill
Requires: python3-apache-airflow-providers-apache-druid
Requires: python3-apache-airflow-providers-apache-hdfs
Requires: python3-apache-airflow-providers-apache-hive
Requires: python3-apache-airflow-providers-apache-pinot
Requires: python3-apache-airflow-providers-arangodb
Requires: python3-apache-airflow-providers-cloudant
Requires: python3-apache-airflow-providers-databricks
Requires: python3-apache-airflow-providers-exasol
Requires: python3-apache-airflow-providers-influxdb
Requires: python3-apache-airflow-providers-microsoft-mssql
Requires: python3-apache-airflow-providers-mongo
Requires: python3-apache-airflow-providers-mysql
Requires: python3-apache-airflow-providers-neo4j
Requires: python3-apache-airflow-providers-postgres
Requires: python3-apache-airflow-providers-presto
Requires: python3-apache-airflow-providers-trino
Requires: python3-apache-airflow-providers-vertica
Requires: python3-mysql-connector-python
Requires: python3-mysqlclient
Requires: python3-sasl
Requires: python3-apache-airflow-providers-amazon
Requires: python3-atlasclient
Requires: python3-apache-airflow-providers-apache-beam
Requires: python3-apache-airflow-providers-apache-cassandra
Requires: python3-apache-airflow-providers-apache-drill
Requires: python3-apache-airflow-providers-apache-druid
Requires: python3-apache-airflow-providers-apache-hdfs
Requires: python3-apache-airflow-providers-apache-hive
Requires: python3-apache-airflow-providers-apache-kylin
Requires: python3-apache-airflow-providers-apache-livy
Requires: python3-apache-airflow-providers-apache-pig
Requires: python3-apache-airflow-providers-apache-pinot
Requires: python3-apache-airflow-providers-apache-spark
Requires: python3-apache-airflow-providers-apache-sqoop
Requires: python3-hdfs[avro,dataframe,kerberos]
Requires: python3-apache-airflow-providers-arangodb
Requires: python3-apache-airflow-providers-asana
Requires: python3-eventlet
Requires: python3-gevent
Requires: python3-greenlet
Requires: python3-apache-airflow-providers-apache-atlas
Requires: python3-apache-airflow-providers-atlassian-jira
Requires: python3-apache-airflow-providers-amazon
Requires: python3-apache-airflow-providers-microsoft-azure
Requires: python3-apache-airflow-providers-apache-cassandra
Requires: python3-apache-airflow
Requires: python3-celery
Requires: python3-flower
Requires: python3-apache-airflow-providers-celery
Requires: python3-cgroupspy
Requires: python3-apache-airflow-providers-cloudant
Requires: python3-apache-airflow
Requires: python3-cryptography
Requires: python3-kubernetes
Requires: python3-apache-airflow-providers-cncf-kubernetes
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-cloudpickle
Requires: python3-dask
Requires: python3-distributed
Requires: python3-apache-airflow-providers-databricks
Requires: python3-apache-airflow-providers-datadog
Requires: python3-apache-airflow-providers-dbt-cloud
Requires: python3-requests
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-apache-airflow
Requires: python3-astroid
Requires: python3-asynctest
Requires: python3-aws-xray-sdk
Requires: python3-bcrypt
Requires: python3-beautifulsoup4
Requires: python3-black
Requires: python3-blinker
Requires: python3-bowler
Requires: python3-cgroupspy
Requires: python3-checksumdir
Requires: python3-click
Requires: python3-coverage
Requires: python3-cryptography
Requires: python3-docutils
Requires: python3-eralchemy2
Requires: python3-filelock
Requires: python3-flake8-colors
Requires: python3-flake8-implicit-str-concat
Requires: python3-flake8
Requires: python3-flaky
Requires: python3-flask-bcrypt
Requires: python3-freezegun
Requires: python3-gitpython
Requires: python3-ipdb
Requires: python3-isort
Requires: python3-jira
Requires: python3-jsondiff
Requires: python3-kubernetes
Requires: python3-mongomock
Requires: python3-moto[cloudformation,glue]
Requires: python3-mypy
Requires: python3-pandas
Requires: python3-parameterized
Requires: python3-paramiko
Requires: python3-pipdeptree
Requires: python3-pre-commit
Requires: python3-pygithub
Requires: python3-pypsrp
Requires: python3-pytest
Requires: python3-pytest-asyncio
Requires: python3-pytest-capture-warnings
Requires: python3-pytest-cov
Requires: python3-pytest-httpx
Requires: python3-pytest-instafail
Requires: python3-pytest-rerunfailures
Requires: python3-pytest-timeouts
Requires: python3-pytest-xdist
Requires: python3-jose
Requires: python3-pywinrm
Requires: python3-qds-sdk
Requires: python3-requests-mock
Requires: python3-rich-click
Requires: python3-semver
Requires: python3-sphinx-airflow-theme
Requires: python3-sphinx-argparse
Requires: python3-sphinx-autoapi
Requires: python3-sphinx-copybutton
Requires: python3-sphinx-jinja
Requires: python3-sphinx-rtd-theme
Requires: python3-sphinx
Requires: python3-sphinxcontrib-httpdomain
Requires: python3-sphinxcontrib-redoc
Requires: python3-sphinxcontrib-spelling
Requires: python3-time-machine
Requires: python3-towncrier
Requires: python3-twine
Requires: python3-types-Deprecated
Requires: python3-types-Markdown
Requires: python3-types-PyMySQL
Requires: python3-types-PyYAML
Requires: python3-types-boto
Requires: python3-types-certifi
Requires: python3-types-croniter
Requires: python3-types-docutils
Requires: python3-types-freezegun
Requires: python3-types-paramiko
Requires: python3-types-protobuf
Requires: python3-types-python-dateutil
Requires: python3-types-python-slugify
Requires: python3-types-pytz
Requires: python3-types-redis
Requires: python3-types-requests
Requires: python3-types-setuptools
Requires: python3-types-tabulate
Requires: python3-types-termcolor
Requires: python3-types-toml
Requires: python3-wheel
Requires: python3-yamllint
Requires: python3-mysql-connector-python
Requires: python3-mysqlclient
Requires: python3-importlib-metadata
Requires: python3-JIRA
Requires: python3-PyOpenSSL
Requires: python3-adal
Requires: python3-aiohttp
Requires: python3-amqp
Requires: python3-analytics-python
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-apache-airflow
Requires: python3-apache-airflow
Requires: python3-apache-beam
Requires: python3-arrow
Requires: python3-asana
Requires: python3-asgiref
Requires: python3-astroid
Requires: python3-asynctest
Requires: python3-atlasclient
Requires: python3-authlib
Requires: python3-aws-xray-sdk
Requires: python3-azure-batch
Requires: python3-azure-cosmos
Requires: python3-azure-datalake-store
Requires: python3-azure-identity
Requires: python3-azure-keyvault-secrets
Requires: python3-azure-kusto-data
Requires: python3-azure-mgmt-containerinstance
Requires: python3-azure-mgmt-datafactory
Requires: python3-azure-mgmt-datalake-store
Requires: python3-azure-mgmt-resource
Requires: python3-azure-storage-blob
Requires: python3-azure-storage-common
Requires: python3-azure-storage-file
Requires: python3-azure-synapse-spark
Requires: python3-bcrypt
Requires: python3-beautifulsoup4
Requires: python3-black
Requires: python3-blinker
Requires: python3-blinker
Requires: python3-boto3
Requires: python3-bowler
Requires: python3-cassandra-driver
Requires: python3-celery
Requires: python3-cgroupspy
Requires: python3-checksumdir
Requires: python3-click
Requires: python3-cloudant
Requires: python3-cloudpickle
Requires: python3-coverage
Requires: python3-cryptography
Requires: python3-dask
Requires: python3-databricks-sql-connector
Requires: python3-datadog
Requires: python3-distributed
Requires: python3-dnspython
Requires: python3-docker
Requires: python3-docutils
Requires: python3-elasticsearch-dbapi
Requires: python3-elasticsearch-dsl
Requires: python3-elasticsearch
Requires: python3-eralchemy2
Requires: python3-eventlet
Requires: python3-facebook-business
Requires: python3-filelock
Requires: python3-flake8-colors
Requires: python3-flake8-implicit-str-concat
Requires: python3-flake8
Requires: python3-flaky
Requires: python3-flask-appbuilder[oauth]
Requires: python3-flask-bcrypt
Requires: python3-flower
Requires: python3-freezegun
Requires: python3-gcloud-aio-bigquery
Requires: python3-gcloud-aio-storage
Requires: python3-gcloud-aio-auth
Requires: python3-gevent
Requires: python3-gitpython
Requires: python3-google-ads
Requires: python3-google-api-core
Requires: python3-google-api-python-client
Requires: python3-google-auth-httplib2
Requires: python3-google-auth
Requires: python3-google-auth
Requires: python3-google-cloud-aiplatform
Requires: python3-google-cloud-automl
Requires: python3-google-cloud-bigquery-datatransfer
Requires: python3-google-cloud-bigtable
Requires: python3-google-cloud-build
Requires: python3-google-cloud-compute
Requires: python3-google-cloud-container
Requires: python3-google-cloud-datacatalog
Requires: python3-google-cloud-dataform
Requires: python3-google-cloud-dataplex
Requires: python3-google-cloud-dataproc-metastore
Requires: python3-google-cloud-dataproc
Requires: python3-google-cloud-dlp
Requires: python3-google-cloud-kms
Requires: python3-google-cloud-language
Requires: python3-google-cloud-logging
Requires: python3-google-cloud-memcache
Requires: python3-google-cloud-monitoring
Requires: python3-google-cloud-orchestration-airflow
Requires: python3-google-cloud-os-login
Requires: python3-google-cloud-pubsub
Requires: python3-google-cloud-redis
Requires: python3-google-cloud-secret-manager
Requires: python3-google-cloud-spanner
Requires: python3-google-cloud-speech
Requires: python3-google-cloud-storage
Requires: python3-google-cloud-tasks
Requires: python3-google-cloud-texttospeech
Requires: python3-google-cloud-translate
Requires: python3-google-cloud-videointelligence
Requires: python3-google-cloud-vision
Requires: python3-google-cloud-workflows
Requires: python3-greenlet
Requires: python3-grpcio-gcp
Requires: python3-grpcio
Requires: python3-hdfs[avro,dataframe,kerberos]
Requires: python3-hmsclient
Requires: python3-httpx
Requires: python3-hvac
Requires: python3-influxdb-client
Requires: python3-ipdb
Requires: python3-isort
Requires: python3-jaydebeapi
Requires: python3-jira
Requires: python3-json-merge-patch
Requires: python3-jsondiff
Requires: python3-jsonpath-ng
Requires: python3-kubernetes
Requires: python3-kylinpy
Requires: python3-ldap3
Requires: python3-looker-sdk
Requires: python3-mongomock
Requires: python3-moto[cloudformation,glue]
Requires: python3-mypy-boto3-appflow
Requires: python3-mypy-boto3-rds
Requires: python3-mypy-boto3-redshift-data
Requires: python3-mypy
Requires: python3-neo4j
Requires: python3-opsgenie-sdk
Requires: python3-oracledb
Requires: python3-oss2
Requires: python3-pandas-gbq
Requires: python3-pandas
Requires: python3-papermill[all]
Requires: python3-parameterized
Requires: python3-paramiko
Requires: python3-paramiko
Requires: python3-pdpyras
Requires: python3-pinotdb
Requires: python3-pipdeptree
Requires: python3-plyvel
Requires: python3-pre-commit
Requires: python3-presto-python-client
Requires: python3-proto-plus
Requires: python3-protobuf
Requires: python3-psycopg2
Requires: python3-pydruid
Requires: python3-pyexasol
Requires: python3-pygithub
Requires: python3-pyhive[hive]
Requires: python3-pykerberos
Requires: python3-pymongo
Requires: python3-pymssql
Requires: python3-pyodbc
Requires: python3-pypsrp
Requires: python3-pypsrp
Requires: python3-pyspark
Requires: python3-pytest
Requires: python3-pytest-asyncio
Requires: python3-pytest-capture-warnings
Requires: python3-pytest-cov
Requires: python3-pytest-httpx
Requires: python3-pytest-instafail
Requires: python3-pytest-rerunfailures
Requires: python3-pytest-timeouts
Requires: python3-pytest-xdist
Requires: python3-arango
Requires: python3-dotenv
Requires: python3-jenkins
Requires: python3-jose
Requires: python3-ldap
Requires: python3-telegram-bot
Requires: python3-pywinrm
Requires: python3-pywinrm
Requires: python3-qds-sdk
Requires: python3-qds-sdk
Requires: python3-redis
Requires: python3-redshift-connector
Requires: python3-requests
Requires: python3-requests
Requires: python3-requests-kerberos
Requires: python3-requests-mock
Requires: python3-requests-toolbelt
Requires: python3-rich-click
Requires: python3-scrapbook[all]
Requires: python3-semver
Requires: python3-sendgrid
Requires: python3-sentry-sdk
Requires: python3-simple-salesforce
Requires: python3-slack-sdk
Requires: python3-smbprotocol
Requires: python3-snowflake-connector-python
Requires: python3-snowflake-sqlalchemy
Requires: python3-sphinx-airflow-theme
Requires: python3-sphinx-argparse
Requires: python3-sphinx-autoapi
Requires: python3-sphinx-copybutton
Requires: python3-sphinx-jinja
Requires: python3-sphinx-rtd-theme
Requires: python3-sphinx
Requires: python3-sphinxcontrib-httpdomain
Requires: python3-sphinxcontrib-redoc
Requires: python3-sphinxcontrib-spelling
Requires: python3-spython
Requires: python3-sqlalchemy-bigquery
Requires: python3-sqlalchemy-drill
Requires: python3-sqlalchemy-redshift
Requires: python3-sqlparse
Requires: python3-sshtunnel
Requires: python3-statsd
Requires: python3-tableauserverclient
Requires: python3-thrift
Requires: python3-thrift-sasl
Requires: python3-time-machine
Requires: python3-towncrier
Requires: python3-trino
Requires: python3-twine
Requires: python3-types-Deprecated
Requires: python3-types-Markdown
Requires: python3-types-PyMySQL
Requires: python3-types-PyYAML
Requires: python3-types-boto
Requires: python3-types-certifi
Requires: python3-types-croniter
Requires: python3-types-docutils
Requires: python3-types-freezegun
Requires: python3-types-paramiko
Requires: python3-types-protobuf
Requires: python3-types-python-dateutil
Requires: python3-types-python-slugify
Requires: python3-types-pytz
Requires: python3-types-redis
Requires: python3-types-requests
Requires: python3-types-setuptools
Requires: python3-types-tabulate
Requires: python3-types-termcolor
Requires: python3-types-toml
Requires: python3-vertica-python
Requires: python3-virtualenv
Requires: python3-watchtower
Requires: python3-wheel
Requires: python3-yamllint
Requires: python3-yandexcloud
Requires: python3-zenpy
Requires: python3-apache-airflow-providers-airbyte
Requires: python3-apache-airflow-providers-alibaba
Requires: python3-apache-airflow-providers-amazon
Requires: python3-apache-airflow-providers-apache-beam
Requires: python3-apache-airflow-providers-apache-cassandra
Requires: python3-apache-airflow-providers-apache-drill
Requires: python3-apache-airflow-providers-apache-druid
Requires: python3-apache-airflow-providers-apache-hdfs
Requires: python3-apache-airflow-providers-apache-hive
Requires: python3-apache-airflow-providers-apache-kylin
Requires: python3-apache-airflow-providers-apache-livy
Requires: python3-apache-airflow-providers-apache-pig
Requires: python3-apache-airflow-providers-apache-pinot
Requires: python3-apache-airflow-providers-apache-spark
Requires: python3-apache-airflow-providers-apache-sqoop
Requires: python3-apache-airflow-providers-arangodb
Requires: python3-apache-airflow-providers-asana
Requires: python3-apache-airflow-providers-atlassian-jira
Requires: python3-apache-airflow-providers-celery
Requires: python3-apache-airflow-providers-cloudant
Requires: python3-apache-airflow-providers-cncf-kubernetes
Requires: python3-apache-airflow-providers-databricks
Requires: python3-apache-airflow-providers-datadog
Requires: python3-apache-airflow-providers-dbt-cloud
Requires: python3-apache-airflow-providers-dingding
Requires: python3-apache-airflow-providers-discord
Requires: python3-apache-airflow-providers-docker
Requires: python3-apache-airflow-providers-elasticsearch
Requires: python3-apache-airflow-providers-exasol
Requires: python3-apache-airflow-providers-facebook
Requires: python3-apache-airflow-providers-ftp
Requires: python3-apache-airflow-providers-github
Requires: python3-apache-airflow-providers-google
Requires: python3-apache-airflow-providers-grpc
Requires: python3-apache-airflow-providers-hashicorp
Requires: python3-apache-airflow-providers-http
Requires: python3-apache-airflow-providers-imap
Requires: python3-apache-airflow-providers-influxdb
Requires: python3-apache-airflow-providers-jdbc
Requires: python3-apache-airflow-providers-jenkins
Requires: python3-apache-airflow-providers-microsoft-azure
Requires: python3-apache-airflow-providers-microsoft-mssql
Requires: python3-apache-airflow-providers-microsoft-psrp
Requires: python3-apache-airflow-providers-microsoft-winrm
Requires: python3-apache-airflow-providers-mongo
Requires: python3-apache-airflow-providers-mysql
Requires: python3-apache-airflow-providers-neo4j
Requires: python3-apache-airflow-providers-odbc
Requires: python3-apache-airflow-providers-openfaas
Requires: python3-apache-airflow-providers-opsgenie
Requires: python3-apache-airflow-providers-oracle
Requires: python3-apache-airflow-providers-pagerduty
Requires: python3-apache-airflow-providers-papermill
Requires: python3-apache-airflow-providers-plexus
Requires: python3-apache-airflow-providers-postgres
Requires: python3-apache-airflow-providers-presto
Requires: python3-apache-airflow-providers-qubole
Requires: python3-apache-airflow-providers-redis
Requires: python3-apache-airflow-providers-salesforce
Requires: python3-apache-airflow-providers-samba
Requires: python3-apache-airflow-providers-segment
Requires: python3-apache-airflow-providers-sendgrid
Requires: python3-apache-airflow-providers-sftp
Requires: python3-apache-airflow-providers-singularity
Requires: python3-apache-airflow-providers-slack
Requires: python3-apache-airflow-providers-snowflake
Requires: python3-apache-airflow-providers-sqlite
Requires: python3-apache-airflow-providers-ssh
Requires: python3-apache-airflow-providers-tableau
Requires: python3-apache-airflow-providers-tabular
Requires: python3-apache-airflow-providers-telegram
Requires: python3-apache-airflow-providers-trino
Requires: python3-apache-airflow-providers-vertica
Requires: python3-apache-airflow-providers-yandex
Requires: python3-apache-airflow-providers-zendesk
Requires: python3-azure-servicebus
Requires: python3-mysql-connector-python
Requires: python3-mysqlclient
Requires: python3-importlib-metadata
Requires: python3-sasl
Requires: python3-JIRA
Requires: python3-PyOpenSSL
Requires: python3-adal
Requires: python3-aiohttp
Requires: python3-amqp
Requires: python3-analytics-python
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-apache-airflow
Requires: python3-apache-airflow
Requires: python3-apache-beam
Requires: python3-arrow
Requires: python3-asana
Requires: python3-asgiref
Requires: python3-astroid
Requires: python3-asynctest
Requires: python3-atlasclient
Requires: python3-authlib
Requires: python3-aws-xray-sdk
Requires: python3-azure-batch
Requires: python3-azure-cosmos
Requires: python3-azure-datalake-store
Requires: python3-azure-identity
Requires: python3-azure-keyvault-secrets
Requires: python3-azure-kusto-data
Requires: python3-azure-mgmt-containerinstance
Requires: python3-azure-mgmt-datafactory
Requires: python3-azure-mgmt-datalake-store
Requires: python3-azure-mgmt-resource
Requires: python3-azure-storage-blob
Requires: python3-azure-storage-common
Requires: python3-azure-storage-file
Requires: python3-azure-synapse-spark
Requires: python3-bcrypt
Requires: python3-beautifulsoup4
Requires: python3-black
Requires: python3-blinker
Requires: python3-blinker
Requires: python3-boto3
Requires: python3-bowler
Requires: python3-cassandra-driver
Requires: python3-celery
Requires: python3-cgroupspy
Requires: python3-checksumdir
Requires: python3-click
Requires: python3-cloudant
Requires: python3-cloudpickle
Requires: python3-coverage
Requires: python3-cryptography
Requires: python3-dask
Requires: python3-databricks-sql-connector
Requires: python3-datadog
Requires: python3-distributed
Requires: python3-dnspython
Requires: python3-docker
Requires: python3-docutils
Requires: python3-elasticsearch-dbapi
Requires: python3-elasticsearch-dsl
Requires: python3-elasticsearch
Requires: python3-eralchemy2
Requires: python3-eventlet
Requires: python3-facebook-business
Requires: python3-filelock
Requires: python3-flake8-colors
Requires: python3-flake8-implicit-str-concat
Requires: python3-flake8
Requires: python3-flaky
Requires: python3-flask-appbuilder[oauth]
Requires: python3-flask-bcrypt
Requires: python3-flower
Requires: python3-freezegun
Requires: python3-gcloud-aio-bigquery
Requires: python3-gcloud-aio-storage
Requires: python3-gcloud-aio-auth
Requires: python3-gevent
Requires: python3-gitpython
Requires: python3-google-ads
Requires: python3-google-api-core
Requires: python3-google-api-python-client
Requires: python3-google-auth-httplib2
Requires: python3-google-auth
Requires: python3-google-auth
Requires: python3-google-cloud-aiplatform
Requires: python3-google-cloud-automl
Requires: python3-google-cloud-bigquery-datatransfer
Requires: python3-google-cloud-bigtable
Requires: python3-google-cloud-build
Requires: python3-google-cloud-compute
Requires: python3-google-cloud-container
Requires: python3-google-cloud-datacatalog
Requires: python3-google-cloud-dataform
Requires: python3-google-cloud-dataplex
Requires: python3-google-cloud-dataproc-metastore
Requires: python3-google-cloud-dataproc
Requires: python3-google-cloud-dlp
Requires: python3-google-cloud-kms
Requires: python3-google-cloud-language
Requires: python3-google-cloud-logging
Requires: python3-google-cloud-memcache
Requires: python3-google-cloud-monitoring
Requires: python3-google-cloud-orchestration-airflow
Requires: python3-google-cloud-os-login
Requires: python3-google-cloud-pubsub
Requires: python3-google-cloud-redis
Requires: python3-google-cloud-secret-manager
Requires: python3-google-cloud-spanner
Requires: python3-google-cloud-speech
Requires: python3-google-cloud-storage
Requires: python3-google-cloud-tasks
Requires: python3-google-cloud-texttospeech
Requires: python3-google-cloud-translate
Requires: python3-google-cloud-videointelligence
Requires: python3-google-cloud-vision
Requires: python3-google-cloud-workflows
Requires: python3-greenlet
Requires: python3-grpcio-gcp
Requires: python3-grpcio
Requires: python3-hdfs[avro,dataframe,kerberos]
Requires: python3-hmsclient
Requires: python3-httpx
Requires: python3-hvac
Requires: python3-influxdb-client
Requires: python3-ipdb
Requires: python3-isort
Requires: python3-jaydebeapi
Requires: python3-jira
Requires: python3-json-merge-patch
Requires: python3-jsondiff
Requires: python3-jsonpath-ng
Requires: python3-kubernetes
Requires: python3-kylinpy
Requires: python3-ldap3
Requires: python3-looker-sdk
Requires: python3-mongomock
Requires: python3-moto[cloudformation,glue]
Requires: python3-mypy-boto3-appflow
Requires: python3-mypy-boto3-rds
Requires: python3-mypy-boto3-redshift-data
Requires: python3-mypy
Requires: python3-neo4j
Requires: python3-opsgenie-sdk
Requires: python3-oracledb
Requires: python3-oss2
Requires: python3-pandas-gbq
Requires: python3-pandas
Requires: python3-papermill[all]
Requires: python3-parameterized
Requires: python3-paramiko
Requires: python3-paramiko
Requires: python3-pdpyras
Requires: python3-pinotdb
Requires: python3-pipdeptree
Requires: python3-plyvel
Requires: python3-pre-commit
Requires: python3-presto-python-client
Requires: python3-proto-plus
Requires: python3-protobuf
Requires: python3-psycopg2
Requires: python3-pydruid
Requires: python3-pyexasol
Requires: python3-pygithub
Requires: python3-pyhive[hive]
Requires: python3-pykerberos
Requires: python3-pymongo
Requires: python3-pymssql
Requires: python3-pyodbc
Requires: python3-pypsrp
Requires: python3-pypsrp
Requires: python3-pyspark
Requires: python3-pytest
Requires: python3-pytest-asyncio
Requires: python3-pytest-capture-warnings
Requires: python3-pytest-cov
Requires: python3-pytest-httpx
Requires: python3-pytest-instafail
Requires: python3-pytest-rerunfailures
Requires: python3-pytest-timeouts
Requires: python3-pytest-xdist
Requires: python3-arango
Requires: python3-dotenv
Requires: python3-jenkins
Requires: python3-jose
Requires: python3-ldap
Requires: python3-telegram-bot
Requires: python3-pywinrm
Requires: python3-pywinrm
Requires: python3-qds-sdk
Requires: python3-qds-sdk
Requires: python3-redis
Requires: python3-redshift-connector
Requires: python3-requests
Requires: python3-requests
Requires: python3-requests-kerberos
Requires: python3-requests-mock
Requires: python3-requests-toolbelt
Requires: python3-rich-click
Requires: python3-scrapbook[all]
Requires: python3-semver
Requires: python3-sendgrid
Requires: python3-sentry-sdk
Requires: python3-simple-salesforce
Requires: python3-slack-sdk
Requires: python3-smbprotocol
Requires: python3-snowflake-connector-python
Requires: python3-snowflake-sqlalchemy
Requires: python3-sphinx-airflow-theme
Requires: python3-sphinx-argparse
Requires: python3-sphinx-autoapi
Requires: python3-sphinx-copybutton
Requires: python3-sphinx-jinja
Requires: python3-sphinx-rtd-theme
Requires: python3-sphinx
Requires: python3-sphinxcontrib-httpdomain
Requires: python3-sphinxcontrib-redoc
Requires: python3-sphinxcontrib-spelling
Requires: python3-spython
Requires: python3-sqlalchemy-bigquery
Requires: python3-sqlalchemy-drill
Requires: python3-sqlalchemy-redshift
Requires: python3-sqlparse
Requires: python3-sshtunnel
Requires: python3-statsd
Requires: python3-tableauserverclient
Requires: python3-thrift
Requires: python3-thrift-sasl
Requires: python3-time-machine
Requires: python3-towncrier
Requires: python3-trino
Requires: python3-twine
Requires: python3-types-Deprecated
Requires: python3-types-Markdown
Requires: python3-types-PyMySQL
Requires: python3-types-PyYAML
Requires: python3-types-boto
Requires: python3-types-certifi
Requires: python3-types-croniter
Requires: python3-types-docutils
Requires: python3-types-freezegun
Requires: python3-types-paramiko
Requires: python3-types-protobuf
Requires: python3-types-python-dateutil
Requires: python3-types-python-slugify
Requires: python3-types-pytz
Requires: python3-types-redis
Requires: python3-types-requests
Requires: python3-types-setuptools
Requires: python3-types-tabulate
Requires: python3-types-termcolor
Requires: python3-types-toml
Requires: python3-vertica-python
Requires: python3-virtualenv
Requires: python3-watchtower
Requires: python3-wheel
Requires: python3-yamllint
Requires: python3-yandexcloud
Requires: python3-zenpy
Requires: python3-apache-airflow-providers-airbyte
Requires: python3-apache-airflow-providers-alibaba
Requires: python3-apache-airflow-providers-amazon
Requires: python3-apache-airflow-providers-apache-beam
Requires: python3-apache-airflow-providers-apache-cassandra
Requires: python3-apache-airflow-providers-apache-drill
Requires: python3-apache-airflow-providers-apache-druid
Requires: python3-apache-airflow-providers-apache-hdfs
Requires: python3-apache-airflow-providers-apache-hive
Requires: python3-apache-airflow-providers-apache-kylin
Requires: python3-apache-airflow-providers-apache-livy
Requires: python3-apache-airflow-providers-apache-pig
Requires: python3-apache-airflow-providers-apache-pinot
Requires: python3-apache-airflow-providers-apache-spark
Requires: python3-apache-airflow-providers-apache-sqoop
Requires: python3-apache-airflow-providers-arangodb
Requires: python3-apache-airflow-providers-asana
Requires: python3-apache-airflow-providers-atlassian-jira
Requires: python3-apache-airflow-providers-celery
Requires: python3-apache-airflow-providers-cloudant
Requires: python3-apache-airflow-providers-cncf-kubernetes
Requires: python3-apache-airflow-providers-databricks
Requires: python3-apache-airflow-providers-datadog
Requires: python3-apache-airflow-providers-dbt-cloud
Requires: python3-apache-airflow-providers-dingding
Requires: python3-apache-airflow-providers-discord
Requires: python3-apache-airflow-providers-docker
Requires: python3-apache-airflow-providers-elasticsearch
Requires: python3-apache-airflow-providers-exasol
Requires: python3-apache-airflow-providers-facebook
Requires: python3-apache-airflow-providers-ftp
Requires: python3-apache-airflow-providers-github
Requires: python3-apache-airflow-providers-google
Requires: python3-apache-airflow-providers-grpc
Requires: python3-apache-airflow-providers-hashicorp
Requires: python3-apache-airflow-providers-http
Requires: python3-apache-airflow-providers-imap
Requires: python3-apache-airflow-providers-influxdb
Requires: python3-apache-airflow-providers-jdbc
Requires: python3-apache-airflow-providers-jenkins
Requires: python3-apache-airflow-providers-microsoft-azure
Requires: python3-apache-airflow-providers-microsoft-mssql
Requires: python3-apache-airflow-providers-microsoft-psrp
Requires: python3-apache-airflow-providers-microsoft-winrm
Requires: python3-apache-airflow-providers-mongo
Requires: python3-apache-airflow-providers-mysql
Requires: python3-apache-airflow-providers-neo4j
Requires: python3-apache-airflow-providers-odbc
Requires: python3-apache-airflow-providers-openfaas
Requires: python3-apache-airflow-providers-opsgenie
Requires: python3-apache-airflow-providers-oracle
Requires: python3-apache-airflow-providers-pagerduty
Requires: python3-apache-airflow-providers-papermill
Requires: python3-apache-airflow-providers-plexus
Requires: python3-apache-airflow-providers-postgres
Requires: python3-apache-airflow-providers-presto
Requires: python3-apache-airflow-providers-qubole
Requires: python3-apache-airflow-providers-redis
Requires: python3-apache-airflow-providers-salesforce
Requires: python3-apache-airflow-providers-samba
Requires: python3-apache-airflow-providers-segment
Requires: python3-apache-airflow-providers-sendgrid
Requires: python3-apache-airflow-providers-sftp
Requires: python3-apache-airflow-providers-singularity
Requires: python3-apache-airflow-providers-slack
Requires: python3-apache-airflow-providers-snowflake
Requires: python3-apache-airflow-providers-sqlite
Requires: python3-apache-airflow-providers-ssh
Requires: python3-apache-airflow-providers-tableau
Requires: python3-apache-airflow-providers-tabular
Requires: python3-apache-airflow-providers-telegram
Requires: python3-apache-airflow-providers-trino
Requires: python3-apache-airflow-providers-vertica
Requires: python3-apache-airflow-providers-yandex
Requires: python3-apache-airflow-providers-zendesk
Requires: python3-azure-servicebus
Requires: python3-mysql-connector-python
Requires: python3-mysqlclient
Requires: python3-importlib-metadata
Requires: python3-sasl
Requires: python3-apache-airflow-providers-common-sql
Requires: python3-apache-airflow
Requires: python3-astroid
Requires: python3-asynctest
Requires: python3-aws-xray-sdk
Requires: python3-bcrypt
Requires: python3-beautifulsoup4
Requires: python3-black
Requires: python3-blinker
Requires: python3-bowler
Requires: python3-cgroupspy
Requires: python3-checksumdir
Requires: python3-click
Requires: python3-coverage
Requires: python3-cryptography
Requires: python3-docutils
Requires: python3-eralchemy2
Requires: python3-filelock
Requires: python3-flake8-colors
Requires: python3-flake8-implicit-str-concat
Requires: python3-flake8
Requires: python3-flaky
Requires: python3-flask-bcrypt
Requires: python3-freezegun
Requires: python3-gitpython
Requires: python3-hdfs[avro,dataframe,kerberos]
Requires: python3-hmsclient
Requires: python3-ipdb
Requires: python3-isort
Requires: python3-jira
Requires: python3-jsondiff
Requires: python3-kubernetes
Requires: python3-mongomock
Requires: python3-moto[cloudformation,glue]
Requires: python3-mypy
Requires: python3-pandas
Requires: python3-parameterized
Requires: python3-paramiko
Requires: python3-pipdeptree
Requires: python3-pre-commit
Requires: python3-presto-python-client
Requires: python3-pygithub
Requires: python3-pyhive[hive]
Requires: python3-pykerberos
Requires: python3-pypsrp
Requires: python3-pytest
Requires: python3-pytest-asyncio
Requires: python3-pytest-capture-warnings
Requires: python3-pytest-cov
Requires: python3-pytest-httpx
Requires: python3-pytest-instafail
Requires: python3-pytest-rerunfailures
Requires: python3-pytest-timeouts
Requires: python3-pytest-xdist
Requires: python3-jose
Requires: python3-pywinrm
Requires: python3-qds-sdk
Requires: python3-requests-kerberos
Requires: python3-requests-mock
Requires: python3-rich-click
Requires: python3-semver
Requires: python3-snakebite-py3
Requires: python3-sphinx-airflow-theme
Requires: python3-sphinx-argparse
Requires: python3-sphinx-autoapi
Requires: python3-sphinx-copybutton
Requires: python3-sphinx-jinja
Requires: python3-sphinx-rtd-theme
Requires: python3-sphinx
Requires: python3-sphinxcontrib-httpdomain
Requires: python3-sphinxcontrib-redoc
Requires: python3-sphinxcontrib-spelling
Requires: python3-thrift
Requires: python3-thrift-sasl
Requires: python3-time-machine
Requires: python3-towncrier
Requires: python3-twine
Requires: python3-types-Deprecated
Requires: python3-types-Markdown
Requires: python3-types-PyMySQL
Requires: python3-types-PyYAML
Requires: python3-types-boto
Requires: python3-types-certifi
Requires: python3-types-croniter
Requires: python3-types-docutils
Requires: python3-types-freezegun
Requires: python3-types-paramiko
Requires: python3-types-protobuf
Requires: python3-types-python-dateutil
Requires: python3-types-python-slugify
Requires: python3-types-pytz
Requires: python3-types-redis
Requires: python3-types-requests
Requires: python3-types-setuptools
Requires: python3-types-tabulate
Requires: python3-types-termcolor
Requires: python3-types-toml
Requires: python3-wheel
Requires: python3-yamllint
Requires: python3-apache-airflow-providers-apache-hdfs
Requires: python3-apache-airflow-providers-apache-hive
Requires: python3-apache-airflow-providers-presto
Requires: python3-apache-airflow-providers-trino
Requires: python3-mysql-connector-python
Requires: python3-mysqlclient
Requires: python3-importlib-metadata
Requires: python3-sasl
Requires: python3-apache-airflow-providers-dingding
Requires: python3-apache-airflow-providers-discord
Requires: python3-astroid
Requires: python3-checksumdir
Requires: python3-click
Requires: python3-docutils
Requires: python3-eralchemy2
Requires: python3-sphinx-airflow-theme
Requires: python3-sphinx-argparse
Requires: python3-sphinx-autoapi
Requires: python3-sphinx-copybutton
Requires: python3-sphinx-jinja
Requires: python3-sphinx-rtd-theme
Requires: python3-sphinx
Requires: python3-sphinxcontrib-httpdomain
Requires: python3-sphinxcontrib-redoc
Requires: python3-sphinxcontrib-spelling
Requires: python3-importlib-metadata
Requires: python3-eralchemy2
Requires: python3-apache-airflow-providers-docker
Requires: python3-apache-airflow-providers-apache-druid
Requires: python3-apache-airflow-providers-elasticsearch
Requires: python3-apache-airflow-providers-exasol
Requires: python3-apache-airflow-providers-facebook
Requires: python3-apache-airflow-providers-ftp
Requires: python3-apache-airflow-providers-google
Requires: python3-apache-airflow-providers-google
Requires: python3-apache-airflow-providers-github
Requires: python3-authlib
Requires: python3-flask-appbuilder[oauth]
Requires: python3-apache-airflow-providers-google
Requires: python3-authlib
Requires: python3-flask-appbuilder[oauth]
Requires: python3-apache-airflow-providers-grpc
Requires: python3-apache-airflow-providers-hashicorp
Requires: python3-apache-airflow-providers-apache-hdfs
Requires: python3-apache-airflow-providers-apache-hive
Requires: python3-apache-airflow-providers-http
Requires: python3-apache-airflow-providers-imap
Requires: python3-apache-airflow-providers-influxdb
Requires: python3-apache-airflow-providers-jdbc
Requires: python3-apache-airflow-providers-jenkins
Requires: python3-pykerberos
Requires: python3-requests-kerberos
Requires: python3-thrift-sasl
Requires: python3-apache-airflow
Requires: python3-cryptography
Requires: python3-kubernetes
Requires: python3-apache-airflow-providers-cncf-kubernetes
Requires: python3-ldap3
Requires: python3-ldap
Requires: python3-plyvel
Requires: python3-apache-airflow-providers-microsoft-azure
Requires: python3-apache-airflow-providers-microsoft-mssql
Requires: python3-apache-airflow-providers-microsoft-psrp
Requires: python3-apache-airflow-providers-microsoft-winrm
Requires: python3-apache-airflow-providers-mongo
Requires: python3-apache-airflow-providers-microsoft-mssql
Requires: python3-apache-airflow-providers-mysql
Requires: python3-apache-airflow-providers-neo4j
Requires: python3-apache-airflow-providers-odbc
Requires: python3-apache-airflow-providers-openfaas
Requires: python3-apache-airflow-providers-opsgenie
Requires: python3-apache-airflow-providers-oracle
Requires: python3-apache-airflow-providers-pagerduty
Requires: python3-pandas
Requires: python3-apache-airflow-providers-papermill
Requires: python3-bcrypt
Requires: python3-flask-bcrypt
Requires: python3-apache-airflow-providers-apache-pinot
Requires: python3-apache-airflow-providers-plexus
Requires: python3-apache-airflow-providers-postgres
Requires: python3-apache-airflow-providers-presto
Requires: python3-apache-airflow-providers-qubole
Requires: python3-apache-airflow-providers-qubole
Requires: python3-amqp
Requires: python3-apache-airflow-providers-redis
Requires: python3-apache-airflow-providers-amazon
Requires: python3-apache-airflow-providers-salesforce
Requires: python3-apache-airflow-providers-samba
Requires: python3-apache-airflow-providers-segment
Requires: python3-apache-airflow-providers-sendgrid
Requires: python3-blinker
Requires: python3-sentry-sdk
Requires: python3-apache-airflow-providers-sftp
Requires: python3-apache-airflow-providers-singularity
Requires: python3-apache-airflow-providers-slack
Requires: python3-apache-airflow-providers-snowflake
Requires: python3-apache-airflow-providers-apache-spark
Requires: python3-apache-airflow-providers-sqlite
Requires: python3-apache-airflow-providers-ssh
Requires: python3-statsd
Requires: python3-apache-airflow-providers-tableau
Requires: python3-apache-airflow-providers-tabular
Requires: python3-apache-airflow-providers-telegram
Requires: python3-apache-airflow-providers-trino
Requires: python3-apache-airflow-providers-vertica
Requires: python3-virtualenv
Requires: python3-hdfs[avro,dataframe,kerberos]
Requires: python3-apache-airflow-providers-microsoft-winrm
Requires: python3-apache-airflow-providers-yandex
Requires: python3-apache-airflow-providers-zendesk
%description
# Apache Airflow
[](https://badge.fury.io/py/apache-airflow)
[](https://github.com/apache/airflow/actions)
[](https://codecov.io/github/apache/airflow?branch=main)
[](https://www.apache.org/licenses/LICENSE-2.0.txt)
[](https://pypi.org/project/apache-airflow/)
[](https://hub.docker.com/r/apache/airflow)
[](https://hub.docker.com/r/apache/airflow)
[](https://pypi.org/project/apache-airflow/)
[](https://artifacthub.io/packages/search?repo=apache-airflow)
[](https://github.com/psf/black)
[](https://twitter.com/ApacheAirflow)
[](https://s.apache.org/airflow-slack)
[](https://github.com/apache/airflow/graphs/contributors)
[Apache Airflow](https://airflow.apache.org/docs/apache-airflow/stable/) (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows.
When workflows are defined as code, they become more maintainable, versionable, testable, and collaborative.
Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command line utilities make performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress, and troubleshoot issues when needed.
**Table of contents**
- [Project Focus](#project-focus)
- [Principles](#principles)
- [Requirements](#requirements)
- [Getting started](#getting-started)
- [Installing from PyPI](#installing-from-pypi)
- [Official source code](#official-source-code)
- [Convenience packages](#convenience-packages)
- [User Interface](#user-interface)
- [Semantic versioning](#semantic-versioning)
- [Version Life Cycle](#version-life-cycle)
- [Support for Python and Kubernetes versions](#support-for-python-and-kubernetes-versions)
- [Base OS support for reference Airflow images](#base-os-support-for-reference-airflow-images)
- [Approach to dependencies of Airflow](#approach-to-dependencies-of-airflow)
- [Release process for Providers](#release-process-for-providers)
- [Contributing](#contributing)
- [Who uses Apache Airflow?](#who-uses-apache-airflow)
- [Who Maintains Apache Airflow?](#who-maintains-apache-airflow)
- [Can I use the Apache Airflow logo in my presentation?](#can-i-use-the-apache-airflow-logo-in-my-presentation)
- [Airflow merchandise](#airflow-merchandise)
- [Links](#links)
- [Sponsors](#sponsors)
## Project Focus
Airflow works best with workflows that are mostly static and slowly changing. When the DAG structure is similar from one run to the next, it clarifies the unit of work and continuity. Other similar projects include [Luigi](https://github.com/spotify/luigi), [Oozie](https://oozie.apache.org/) and [Azkaban](https://azkaban.github.io/).
Airflow is commonly used to process data, but has the opinion that tasks should ideally be idempotent (i.e., results of the task will be the same, and will not create duplicated data in a destination system), and should not pass large quantities of data from one task to the next (though tasks can pass metadata using Airflow's [XCom feature](https://airflow.apache.org/docs/apache-airflow/stable/concepts/xcoms.html)). For high-volume, data-intensive tasks, a best practice is to delegate to external services specializing in that type of work.
Airflow is not a streaming solution, but it is often used to process real-time data, pulling data off streams in batches.
## Principles
- **Dynamic**: Airflow pipelines are configuration as code (Python), allowing for dynamic pipeline generation. This allows for writing code that instantiates pipelines dynamically.
- **Extensible**: Easily define your own operators, executors and extend the library so that it fits the level of abstraction that suits your environment.
- **Elegant**: Airflow pipelines are lean and explicit. Parameterizing your scripts is built into the core of Airflow using the powerful **Jinja** templating engine.
- **Scalable**: Airflow has a modular architecture and uses a message queue to orchestrate an arbitrary number of workers.
## Requirements
Apache Airflow is tested with:
| | Main version (dev) | Stable version (2.5.3) |
|---------------------|------------------------------|------------------------------|
| Python | 3.7, 3.8, 3.9, 3.10 | 3.7, 3.8, 3.9, 3.10 |
| Platform | AMD64/ARM64(\*) | AMD64/ARM64(\*) |
| Kubernetes | 1.21, 1.22, 1.23, 1.24, 1.25 | 1.21, 1.22, 1.23, 1.24, 1.25 |
| PostgreSQL | 11, 12, 13, 14, 15 | 11, 12, 13, 14, 15 |
| MySQL | 5.7, 8 | 5.7, 8 |
| SQLite | 3.15.0+ | 3.15.0+ |
| MSSQL | 2017(\*), 2019 (\*) | 2017(\*), 2019 (\*) |
\* Experimental
**Note**: MySQL 5.x versions are unable to or have limitations with
running multiple schedulers -- please see the [Scheduler docs](https://airflow.apache.org/docs/apache-airflow/stable/scheduler.html).
MariaDB is not tested/recommended.
**Note**: SQLite is used in Airflow tests. Do not use it in production. We recommend
using the latest stable version of SQLite for local development.
**Note**: Airflow currently can be run on POSIX-compliant Operating Systems. For development it is regularly
tested on fairly modern Linux Distros and recent versions of MacOS.
On Windows you can run it via WSL2 (Windows Subsystem for Linux 2) or via Linux Containers.
The work to add Windows support is tracked via [#10388](https://github.com/apache/airflow/issues/10388) but
it is not a high priority. You should only use Linux-based distros as "Production" execution environment
as this is the only environment that is supported. The only distro that is used in our CI tests and that
is used in the [Community managed DockerHub image](https://hub.docker.com/p/apache/airflow) is
`Debian Bullseye`.
## Getting started
Visit the official Airflow website documentation (latest **stable** release) for help with
[installing Airflow](https://airflow.apache.org/docs/apache-airflow/stable/installation.html),
[getting started](https://airflow.apache.org/docs/apache-airflow/stable/start.html), or walking
through a more complete [tutorial](https://airflow.apache.org/docs/apache-airflow/stable/tutorial.html).
> Note: If you're looking for documentation for the main branch (latest development branch): you can find it on [s.apache.org/airflow-docs](https://s.apache.org/airflow-docs/).
For more information on Airflow Improvement Proposals (AIPs), visit
the [Airflow Wiki](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals).
Documentation for dependent projects like provider packages, Docker image, Helm Chart, you'll find it in [the documentation index](https://airflow.apache.org/docs/).
## Installing from PyPI
We publish Apache Airflow as `apache-airflow` package in PyPI. Installing it however might be sometimes tricky
because Airflow is a bit of both a library and application. Libraries usually keep their dependencies open, and
applications usually pin them, but we should do neither and both simultaneously. We decided to keep
our dependencies as open as possible (in `setup.py`) so users can install different versions of libraries
if needed. This means that `pip install apache-airflow` will not work from time to time or will
produce unusable Airflow installation.
To have repeatable installation, however, we keep a set of "known-to-be-working" constraint
files in the orphan `constraints-main` and `constraints-2-0` branches. We keep those "known-to-be-working"
constraints files separately per major/minor Python version.
You can use them as constraint files when installing Airflow from PyPI. Note that you have to specify
correct Airflow tag/version/branch and Python versions in the URL.
1. Installing just Airflow:
> Note: Only `pip` installation is currently officially supported.
While it is possible to install Airflow with tools like [Poetry](https://python-poetry.org) or
[pip-tools](https://pypi.org/project/pip-tools), they do not share the same workflow as
`pip` - especially when it comes to constraint vs. requirements management.
Installing via `Poetry` or `pip-tools` is not currently supported.
If you wish to install Airflow using those tools, you should use the constraint files and convert
them to the appropriate format and workflow that your tool requires.
```bash
pip install 'apache-airflow==2.5.3' \
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.5.3/constraints-3.7.txt"
```
2. Installing with extras (i.e., postgres, google)
```bash
pip install 'apache-airflow[postgres,google]==2.5.3' \
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.5.3/constraints-3.7.txt"
```
For information on installing provider packages, check
[providers](http://airflow.apache.org/docs/apache-airflow-providers/index.html).
## Official source code
Apache Airflow is an [Apache Software Foundation](https://www.apache.org) (ASF) project,
and our official source code releases:
- Follow the [ASF Release Policy](https://www.apache.org/legal/release-policy.html)
- Can be downloaded from [the ASF Distribution Directory](https://downloads.apache.org/airflow)
- Are cryptographically signed by the release manager
- Are officially voted on by the PMC members during the
[Release Approval Process](https://www.apache.org/legal/release-policy.html#release-approval)
Following the ASF rules, the source packages released must be sufficient for a user to build and test the
release provided they have access to the appropriate platform and tools.
## Convenience packages
There are other ways of installing and using Airflow. Those are "convenience" methods - they are
not "official releases" as stated by the `ASF Release Policy`, but they can be used by the users
who do not want to build the software themselves.
Those are - in the order of most common ways people install Airflow:
- [PyPI releases](https://pypi.org/project/apache-airflow/) to install Airflow using standard `pip` tool
- [Docker Images](https://hub.docker.com/r/apache/airflow) to install airflow via
`docker` tool, use them in Kubernetes, Helm Charts, `docker-compose`, `docker swarm`, etc. You can
read more about using, customising, and extending the images in the
[Latest docs](https://airflow.apache.org/docs/docker-stack/index.html), and
learn details on the internals in the [IMAGES.rst](https://github.com/apache/airflow/blob/main/IMAGES.rst) document.
- [Tags in GitHub](https://github.com/apache/airflow/tags) to retrieve the git project sources that
were used to generate official source packages via git
All those artifacts are not official releases, but they are prepared using officially released sources.
Some of those artifacts are "development" or "pre-release" ones, and they are clearly marked as such
following the ASF Policy.
## User Interface
- **DAGs**: Overview of all DAGs in your environment.
- **Grid**: Grid representation of a DAG that spans across time.
- **Graph**: Visualization of a DAG's dependencies and their current status for a specific run.
- **Task Duration**: Total time spent on different tasks over time.
- **Gantt**: Duration and overlap of a DAG.
- **Code**: Quick way to view source code of a DAG.
## Semantic versioning
As of Airflow 2.0.0, we support a strict [SemVer](https://semver.org/) approach for all packages released.
There are few specific rules that we agreed to that define details of versioning of the different
packages:
* **Airflow**: SemVer rules apply to core airflow only (excludes any changes to providers).
Changing limits for versions of Airflow dependencies is not a breaking change on its own.
* **Airflow Providers**: SemVer rules apply to changes in the particular provider's code only.
SemVer MAJOR and MINOR versions for the packages are independent of the Airflow version.
For example, `google 4.1.0` and `amazon 3.0.3` providers can happily be installed
with `Airflow 2.1.2`. If there are limits of cross-dependencies between providers and Airflow packages,
they are present in providers as `install_requires` limitations. We aim to keep backwards
compatibility of providers with all previously released Airflow 2 versions but
there will sometimes be breaking changes that might make some, or all
providers, have minimum Airflow version specified. Change of that minimum supported Airflow version
is a breaking change for provider because installing the new provider might automatically
upgrade Airflow (which might be an undesired side effect of upgrading provider).
* **Airflow Helm Chart**: SemVer rules apply to changes in the chart only. SemVer MAJOR and MINOR
versions for the chart are independent from the Airflow version. We aim to keep backwards
compatibility of the Helm Chart with all released Airflow 2 versions, but some new features might
only work starting from specific Airflow releases. We might however limit the Helm
Chart to depend on minimal Airflow version.
* **Airflow API clients**: SemVer MAJOR and MINOR versions follow MAJOR and MINOR versions of Airflow.
The first MAJOR or MINOR X.Y.0 release of Airflow should always be followed by X.Y.0 release of
all clients. An airflow PATCH X.Y.Z release can be followed by a PATCH release of API clients, only
if this PATCH is relevant to the clients.
The clients then can release their own PATCH releases with bugfixes, independently of Airflow PATCH releases.
As a consequence, each API client will have its own PATCH version that may or may not be in sync with the Airflow
PATCH version. For a specific MAJOR/MINOR Airflow version, users should favor the latest PATCH version of clients
independently of their Airflow PATCH version.
## Version Life Cycle
Apache Airflow version life cycle:
| Version | Current Patch/Minor | State | First Release | Limited Support | EOL/Terminated |
|-----------|-----------------------|-----------|-----------------|-------------------|------------------|
| 2 | 2.5.3 | Supported | Dec 17, 2020 | TBD | TBD |
| 1.10 | 1.10.15 | EOL | Aug 27, 2018 | Dec 17, 2020 | June 17, 2021 |
| 1.9 | 1.9.0 | EOL | Jan 03, 2018 | Aug 27, 2018 | Aug 27, 2018 |
| 1.8 | 1.8.2 | EOL | Mar 19, 2017 | Jan 03, 2018 | Jan 03, 2018 |
| 1.7 | 1.7.1.2 | EOL | Mar 28, 2016 | Mar 19, 2017 | Mar 19, 2017 |
Limited support versions will be supported with security and critical bug fix only.
EOL versions will not get any fixes nor support.
We always recommend that all users run the latest available minor release for whatever major version is in use.
We **highly** recommend upgrading to the latest Airflow major release at the earliest convenient time and before the EOL date.
## Support for Python and Kubernetes versions
As of Airflow 2.0, we agreed to certain rules we follow for Python and Kubernetes support.
They are based on the official release schedule of Python and Kubernetes, nicely summarized in the
[Python Developer's Guide](https://devguide.python.org/#status-of-python-branches) and
[Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/).
1. We drop support for Python and Kubernetes versions when they reach EOL. Except for Kubernetes, a
version stays supported by Airflow if two major cloud providers still provide support for it. We drop
support for those EOL versions in main right after EOL date, and it is effectively removed when we release
the first new MINOR (Or MAJOR if there is no new MINOR version) of Airflow. For example, for Python 3.7 it
means that we will drop support in main right after 27.06.2023, and the first MAJOR or MINOR version of
Airflow released after will not have it.
2. The "oldest" supported version of Python/Kubernetes is the default one until we decide to switch to
later version. "Default" is only meaningful in terms of "smoke tests" in CI PRs, which are run using this
default version and the default reference image available. Currently `apache/airflow:latest`
and `apache/airflow:2.5.3` images are Python 3.7 images. This means that default reference image will
become the default at the time when we start preparing for dropping 3.7 support which is few months
before the end of life for Python 3.7.
3. We support a new version of Python/Kubernetes in main after they are officially released, as soon as we
make them work in our CI pipeline (which might not be immediate due to dependencies catching up with
new versions of Python mostly) we release new images/support in Airflow based on the working CI setup.
## Base OS support for reference Airflow images
The Airflow Community provides conveniently packaged container images that are published whenever
we publish an Apache Airflow release. Those images contain:
* Base OS with necessary packages to install Airflow (stable Debian OS)
* Base Python installation in versions supported at the time of release for the MINOR version of
Airflow released (so there could be different versions for 2.3 and 2.2 line for example)
* Libraries required to connect to suppoerted Databases (again the set of databases supported depends
on the MINOR version of Airflow.
* Predefined set of popular providers (for details see the [Dockerfile](https://raw.githubusercontent.com/apache/airflow/main/Dockerfile)).
* Possibility of building your own, custom image where the user can choose their own set of providers
and libraries (see [Building the image](https://airflow.apache.org/docs/docker-stack/build.html))
* In the future Airflow might also support a "slim" version without providers nor database clients installed
The version of the base OS image is the stable version of Debian. Airflow supports using all currently active
stable versions - as soon as all Airflow dependencies support building, and we set up the CI pipeline for
building and testing the OS version. Approximately 6 months before the end-of-life of a previous stable
version of the OS, Airflow switches the images released to use the latest supported version of the OS.
For example since ``Debian Buster`` end-of-life was August 2022, Airflow switched the images in `main` branch
to use ``Debian Bullseye`` in February/March 2022. The version was used in the next MINOR release after
the switch happened. In case of the Bullseye switch - 2.3.0 version used ``Debian Bullseye``.
The images released in the previous MINOR version continue to use the version that all other releases
for the MINOR version used.
Support for ``Debian Buster`` image was dropped in August 2022 completely and everyone is expected to
stop building their images using ``Debian Buster``.
Users will continue to be able to build their images using stable Debian releases until the end of life and
building and verifying of the images happens in our CI but no unit tests were executed using this image in
the `main` branch.
## Approach to dependencies of Airflow
Airflow has a lot of dependencies - direct and transitive, also Airflow is both - library and application,
therefore our policies to dependencies has to include both - stability of installation of application,
but also ability to install newer version of dependencies for those users who develop DAGs. We developed
the approach where `constraints` are used to make sure airflow can be installed in a repeatable way, while
we do not limit our users to upgrade most of the dependencies. As a result we decided not to upper-bound
version of Airflow dependencies by default, unless we have good reasons to believe upper-bounding them is
needed because of importance of the dependency as well as risk it involves to upgrade specific dependency.
We also upper-bound the dependencies that we know cause problems.
The constraint mechanism of ours takes care about finding and upgrading all the non-upper bound dependencies
automatically (providing that all the tests pass). Our `main` build failures will indicate in case there
are versions of dependencies that break our tests - indicating that we should either upper-bind them or
that we should fix our code/tests to account for the upstream changes from those dependencies.
Whenever we upper-bound such a dependency, we should always comment why we are doing it - i.e. we should have
a good reason why dependency is upper-bound. And we should also mention what is the condition to remove the
binding.
### Approach for dependencies for Airflow Core
Those `extras` and `providers` dependencies are maintained in `setup.cfg`.
There are few dependencies that we decided are important enough to upper-bound them by default, as they are
known to follow predictable versioning scheme, and we know that new versions of those are very likely to
bring breaking changes. We commit to regularly review and attempt to upgrade to the newer versions of
the dependencies as they are released, but this is manual process.
The important dependencies are:
* `SQLAlchemy`: upper-bound to specific MINOR version (SQLAlchemy is known to remove deprecations and
introduce breaking changes especially that support for different Databases varies and changes at
various speed (example: SQLAlchemy 1.4 broke MSSQL integration for Airflow)
* `Alembic`: it is important to handle our migrations in predictable and performant way. It is developed
together with SQLAlchemy. Our experience with Alembic is that it very stable in MINOR version
* `Flask`: We are using Flask as the back-bone of our web UI and API. We know major version of Flask
are very likely to introduce breaking changes across those so limiting it to MAJOR version makes sense
* `werkzeug`: the library is known to cause problems in new versions. It is tightly coupled with Flask
libraries, and we should update them together
* `celery`: Celery is crucial component of Airflow as it used for CeleryExecutor (and similar). Celery
[follows SemVer](https://docs.celeryq.dev/en/stable/contributing.html?highlight=semver#versions), so
we should upper-bound it to the next MAJOR version. Also when we bump the upper version of the library,
we should make sure Celery Provider minimum Airflow version is updated).
* `kubernetes`: Kubernetes is a crucial component of Airflow as it is used for the KubernetesExecutor
(and similar). Kubernetes Python library [follows SemVer](https://github.com/kubernetes-client/python#compatibility),
so we should upper-bound it to the next MAJOR version. Also when we bump the upper version of the library,
we should make sure Kubernetes Provider minimum Airflow version is updated.
### Approach for dependencies in Airflow Providers and extras
Those `extras` and `providers` dependencies are maintained in `provider.yaml` of each provider.
By default, we should not upper-bound dependencies for providers, however each provider's maintainer
might decide to add additional limits (and justify them with comment)
## Release process for Providers
Providers released by the community (with roughly monthly cadence) have
limitation of a minimum supported version of Airflow. The minimum version of
Airflow is the `MINOR` version (2.2, 2.3 etc.) indicating that the providers
might use features that appeared in this release. The default support timespan
for the minimum version of Airflow (there could be justified exceptions) is
that we increase the minimum Airflow version, when 12 months passed since the
first release for the MINOR version of Airflow.
For example this means that by default we upgrade the minimum version of Airflow supported by providers
to 2.4.0 in the first Provider's release after 30th of April 2023. The 30th of April 2022 is the date when the
first `PATCHLEVEL` of 2.3 (2.3.0) has been released.
When we increase the minimum Airflow version, this is not a reason to bump `MAJOR` version of the providers
(unless there are other breaking changes in the provider). The reason for that is that people who use
older version of Airflow will not be able to use that provider (so it is not a breaking change for them)
and for people who are using supported version of Airflow this is not a breaking change on its own - they
will be able to use the new version without breaking their workflows. When we upgraded min-version to
2.2+, our approach was different but as of 2.3+ upgrade (November 2022) we only bump `MINOR` version of the
provider when we increase minimum Airflow version.
Providers are often connected with some stakeholders that are vitally interested in maintaining backwards
compatibilities in their integrations (for example cloud providers, or specific service providers). But,
we are also bound with the [Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html)
which describes who releases, and how to release the ASF software. The provider's governance model is something we name
"mixed governance" - where we follow the release policies, while the burden of maintaining and testing
the cherry-picked versions is on those who commit to perform the cherry-picks and make PRs to older
branches.
The "mixed governance" (optional, per-provider) means that:
* The Airflow Community and release manager decide when to release those providers.
This is fully managed by the community and the usual release-management process following the
[Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html)
* The contributors (who might or might not be direct stakeholders in the provider) will carry the burden
of cherry-picking and testing the older versions of providers.
* There is no "selection" and acceptance process to determine which version of the provider is released.
It is determined by the actions of contributors raising the PR with cherry-picked changes and it follows
the usual PR review process where maintainer approves (or not) and merges (or not) such PR. Simply
speaking - the completed action of cherry-picking and testing the older version of the provider make
it eligible to be released. Unless there is someone who volunteers and perform the cherry-picking and
testing, the provider is not released.
* Branches to raise PR against are created when a contributor commits to perform the cherry-picking
(as a comment in PR to cherry-pick for example)
Usually, community effort is focused on the most recent version of each provider. The community approach is
that we should rather aggressively remove deprecations in "major" versions of the providers - whenever
there is an opportunity to increase major version of a provider, we attempt to remove all deprecations.
However, sometimes there is a contributor (who might or might not represent stakeholder),
willing to make their effort on cherry-picking and testing the non-breaking changes to a selected,
previous major branch of the provider. This results in releasing at most two versions of a
provider at a time:
* potentially breaking "latest" major version
* selected past major version with non-breaking changes applied by the contributor
Cherry-picking such changes follows the same process for releasing Airflow
patch-level releases for a previous minor Airflow version. Usually such cherry-picking is done when
there is an important bugfix and the latest version contains breaking changes that are not
coupled with the bugfix. Releasing them together in the latest version of the provider effectively couples
them, and therefore they're released separately. The cherry-picked changes have to be merged by the committer following the usual rules of the
community.
There is no obligation to cherry-pick and release older versions of the providers.
The community continues to release such older versions of the providers for as long as there is an effort
of the contributors to perform the cherry-picks and carry-on testing of the older provider version.
The availability of stakeholder that can manage "service-oriented" maintenance and agrees to such a
responsibility, will also drive our willingness to accept future, new providers to become community managed.
## Contributing
Want to help build Apache Airflow? Check out our [contributing documentation](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst).
Official Docker (container) images for Apache Airflow are described in [IMAGES.rst](https://github.com/apache/airflow/blob/main/IMAGES.rst).
## Who uses Apache Airflow?
More than 400 organizations are using Apache Airflow
[in the wild](https://github.com/apache/airflow/blob/main/INTHEWILD.md).
## Who Maintains Apache Airflow?
Airflow is the work of the [community](https://github.com/apache/airflow/graphs/contributors),
but the [core committers/maintainers](https://people.apache.org/committers-by-project.html#airflow)
are responsible for reviewing and merging PRs as well as steering conversations around new feature requests.
If you would like to become a maintainer, please review the Apache Airflow
[committer requirements](https://github.com/apache/airflow/blob/main/COMMITTERS.rst#guidelines-to-become-an-airflow-committer).
## Can I use the Apache Airflow logo in my presentation?
Yes! Be sure to abide by the Apache Foundation [trademark policies](https://www.apache.org/foundation/marks/#books) and the Apache Airflow [Brandbook](https://cwiki.apache.org/confluence/display/AIRFLOW/Brandbook). The most up to date logos are found in [this repo](/docs/apache-airflow/img/logos) and on the Apache Software Foundation [website](https://www.apache.org/logos/about.html).
## Airflow merchandise
If you would love to have Apache Airflow stickers, t-shirt, etc. then check out
[Redbubble Shop](https://www.redbubble.com/i/sticker/Apache-Airflow-by-comdev/40497530.EJUG5).
## Links
- [Documentation](https://airflow.apache.org/docs/apache-airflow/stable/)
- [Chat](https://s.apache.org/airflow-slack)
## Sponsors
The CI infrastructure for Apache Airflow has been sponsored by:
%package -n python3-apache-airflow
Summary: Programmatically author, schedule and monitor data pipelines
Provides: python-apache-airflow
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-apache-airflow
# Apache Airflow
[](https://badge.fury.io/py/apache-airflow)
[](https://github.com/apache/airflow/actions)
[](https://codecov.io/github/apache/airflow?branch=main)
[](https://www.apache.org/licenses/LICENSE-2.0.txt)
[](https://pypi.org/project/apache-airflow/)
[](https://hub.docker.com/r/apache/airflow)
[](https://hub.docker.com/r/apache/airflow)
[](https://pypi.org/project/apache-airflow/)
[](https://artifacthub.io/packages/search?repo=apache-airflow)
[](https://github.com/psf/black)
[](https://twitter.com/ApacheAirflow)
[](https://s.apache.org/airflow-slack)
[](https://github.com/apache/airflow/graphs/contributors)
[Apache Airflow](https://airflow.apache.org/docs/apache-airflow/stable/) (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows.
When workflows are defined as code, they become more maintainable, versionable, testable, and collaborative.
Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command line utilities make performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress, and troubleshoot issues when needed.
**Table of contents**
- [Project Focus](#project-focus)
- [Principles](#principles)
- [Requirements](#requirements)
- [Getting started](#getting-started)
- [Installing from PyPI](#installing-from-pypi)
- [Official source code](#official-source-code)
- [Convenience packages](#convenience-packages)
- [User Interface](#user-interface)
- [Semantic versioning](#semantic-versioning)
- [Version Life Cycle](#version-life-cycle)
- [Support for Python and Kubernetes versions](#support-for-python-and-kubernetes-versions)
- [Base OS support for reference Airflow images](#base-os-support-for-reference-airflow-images)
- [Approach to dependencies of Airflow](#approach-to-dependencies-of-airflow)
- [Release process for Providers](#release-process-for-providers)
- [Contributing](#contributing)
- [Who uses Apache Airflow?](#who-uses-apache-airflow)
- [Who Maintains Apache Airflow?](#who-maintains-apache-airflow)
- [Can I use the Apache Airflow logo in my presentation?](#can-i-use-the-apache-airflow-logo-in-my-presentation)
- [Airflow merchandise](#airflow-merchandise)
- [Links](#links)
- [Sponsors](#sponsors)
## Project Focus
Airflow works best with workflows that are mostly static and slowly changing. When the DAG structure is similar from one run to the next, it clarifies the unit of work and continuity. Other similar projects include [Luigi](https://github.com/spotify/luigi), [Oozie](https://oozie.apache.org/) and [Azkaban](https://azkaban.github.io/).
Airflow is commonly used to process data, but has the opinion that tasks should ideally be idempotent (i.e., results of the task will be the same, and will not create duplicated data in a destination system), and should not pass large quantities of data from one task to the next (though tasks can pass metadata using Airflow's [XCom feature](https://airflow.apache.org/docs/apache-airflow/stable/concepts/xcoms.html)). For high-volume, data-intensive tasks, a best practice is to delegate to external services specializing in that type of work.
Airflow is not a streaming solution, but it is often used to process real-time data, pulling data off streams in batches.
## Principles
- **Dynamic**: Airflow pipelines are configuration as code (Python), allowing for dynamic pipeline generation. This allows for writing code that instantiates pipelines dynamically.
- **Extensible**: Easily define your own operators, executors and extend the library so that it fits the level of abstraction that suits your environment.
- **Elegant**: Airflow pipelines are lean and explicit. Parameterizing your scripts is built into the core of Airflow using the powerful **Jinja** templating engine.
- **Scalable**: Airflow has a modular architecture and uses a message queue to orchestrate an arbitrary number of workers.
## Requirements
Apache Airflow is tested with:
| | Main version (dev) | Stable version (2.5.3) |
|---------------------|------------------------------|------------------------------|
| Python | 3.7, 3.8, 3.9, 3.10 | 3.7, 3.8, 3.9, 3.10 |
| Platform | AMD64/ARM64(\*) | AMD64/ARM64(\*) |
| Kubernetes | 1.21, 1.22, 1.23, 1.24, 1.25 | 1.21, 1.22, 1.23, 1.24, 1.25 |
| PostgreSQL | 11, 12, 13, 14, 15 | 11, 12, 13, 14, 15 |
| MySQL | 5.7, 8 | 5.7, 8 |
| SQLite | 3.15.0+ | 3.15.0+ |
| MSSQL | 2017(\*), 2019 (\*) | 2017(\*), 2019 (\*) |
\* Experimental
**Note**: MySQL 5.x versions are unable to or have limitations with
running multiple schedulers -- please see the [Scheduler docs](https://airflow.apache.org/docs/apache-airflow/stable/scheduler.html).
MariaDB is not tested/recommended.
**Note**: SQLite is used in Airflow tests. Do not use it in production. We recommend
using the latest stable version of SQLite for local development.
**Note**: Airflow currently can be run on POSIX-compliant Operating Systems. For development it is regularly
tested on fairly modern Linux Distros and recent versions of MacOS.
On Windows you can run it via WSL2 (Windows Subsystem for Linux 2) or via Linux Containers.
The work to add Windows support is tracked via [#10388](https://github.com/apache/airflow/issues/10388) but
it is not a high priority. You should only use Linux-based distros as "Production" execution environment
as this is the only environment that is supported. The only distro that is used in our CI tests and that
is used in the [Community managed DockerHub image](https://hub.docker.com/p/apache/airflow) is
`Debian Bullseye`.
## Getting started
Visit the official Airflow website documentation (latest **stable** release) for help with
[installing Airflow](https://airflow.apache.org/docs/apache-airflow/stable/installation.html),
[getting started](https://airflow.apache.org/docs/apache-airflow/stable/start.html), or walking
through a more complete [tutorial](https://airflow.apache.org/docs/apache-airflow/stable/tutorial.html).
> Note: If you're looking for documentation for the main branch (latest development branch): you can find it on [s.apache.org/airflow-docs](https://s.apache.org/airflow-docs/).
For more information on Airflow Improvement Proposals (AIPs), visit
the [Airflow Wiki](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals).
Documentation for dependent projects like provider packages, Docker image, Helm Chart, you'll find it in [the documentation index](https://airflow.apache.org/docs/).
## Installing from PyPI
We publish Apache Airflow as `apache-airflow` package in PyPI. Installing it however might be sometimes tricky
because Airflow is a bit of both a library and application. Libraries usually keep their dependencies open, and
applications usually pin them, but we should do neither and both simultaneously. We decided to keep
our dependencies as open as possible (in `setup.py`) so users can install different versions of libraries
if needed. This means that `pip install apache-airflow` will not work from time to time or will
produce unusable Airflow installation.
To have repeatable installation, however, we keep a set of "known-to-be-working" constraint
files in the orphan `constraints-main` and `constraints-2-0` branches. We keep those "known-to-be-working"
constraints files separately per major/minor Python version.
You can use them as constraint files when installing Airflow from PyPI. Note that you have to specify
correct Airflow tag/version/branch and Python versions in the URL.
1. Installing just Airflow:
> Note: Only `pip` installation is currently officially supported.
While it is possible to install Airflow with tools like [Poetry](https://python-poetry.org) or
[pip-tools](https://pypi.org/project/pip-tools), they do not share the same workflow as
`pip` - especially when it comes to constraint vs. requirements management.
Installing via `Poetry` or `pip-tools` is not currently supported.
If you wish to install Airflow using those tools, you should use the constraint files and convert
them to the appropriate format and workflow that your tool requires.
```bash
pip install 'apache-airflow==2.5.3' \
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.5.3/constraints-3.7.txt"
```
2. Installing with extras (i.e., postgres, google)
```bash
pip install 'apache-airflow[postgres,google]==2.5.3' \
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.5.3/constraints-3.7.txt"
```
For information on installing provider packages, check
[providers](http://airflow.apache.org/docs/apache-airflow-providers/index.html).
## Official source code
Apache Airflow is an [Apache Software Foundation](https://www.apache.org) (ASF) project,
and our official source code releases:
- Follow the [ASF Release Policy](https://www.apache.org/legal/release-policy.html)
- Can be downloaded from [the ASF Distribution Directory](https://downloads.apache.org/airflow)
- Are cryptographically signed by the release manager
- Are officially voted on by the PMC members during the
[Release Approval Process](https://www.apache.org/legal/release-policy.html#release-approval)
Following the ASF rules, the source packages released must be sufficient for a user to build and test the
release provided they have access to the appropriate platform and tools.
## Convenience packages
There are other ways of installing and using Airflow. Those are "convenience" methods - they are
not "official releases" as stated by the `ASF Release Policy`, but they can be used by the users
who do not want to build the software themselves.
Those are - in the order of most common ways people install Airflow:
- [PyPI releases](https://pypi.org/project/apache-airflow/) to install Airflow using standard `pip` tool
- [Docker Images](https://hub.docker.com/r/apache/airflow) to install airflow via
`docker` tool, use them in Kubernetes, Helm Charts, `docker-compose`, `docker swarm`, etc. You can
read more about using, customising, and extending the images in the
[Latest docs](https://airflow.apache.org/docs/docker-stack/index.html), and
learn details on the internals in the [IMAGES.rst](https://github.com/apache/airflow/blob/main/IMAGES.rst) document.
- [Tags in GitHub](https://github.com/apache/airflow/tags) to retrieve the git project sources that
were used to generate official source packages via git
All those artifacts are not official releases, but they are prepared using officially released sources.
Some of those artifacts are "development" or "pre-release" ones, and they are clearly marked as such
following the ASF Policy.
## User Interface
- **DAGs**: Overview of all DAGs in your environment.
- **Grid**: Grid representation of a DAG that spans across time.
- **Graph**: Visualization of a DAG's dependencies and their current status for a specific run.
- **Task Duration**: Total time spent on different tasks over time.
- **Gantt**: Duration and overlap of a DAG.
- **Code**: Quick way to view source code of a DAG.
## Semantic versioning
As of Airflow 2.0.0, we support a strict [SemVer](https://semver.org/) approach for all packages released.
There are few specific rules that we agreed to that define details of versioning of the different
packages:
* **Airflow**: SemVer rules apply to core airflow only (excludes any changes to providers).
Changing limits for versions of Airflow dependencies is not a breaking change on its own.
* **Airflow Providers**: SemVer rules apply to changes in the particular provider's code only.
SemVer MAJOR and MINOR versions for the packages are independent of the Airflow version.
For example, `google 4.1.0` and `amazon 3.0.3` providers can happily be installed
with `Airflow 2.1.2`. If there are limits of cross-dependencies between providers and Airflow packages,
they are present in providers as `install_requires` limitations. We aim to keep backwards
compatibility of providers with all previously released Airflow 2 versions but
there will sometimes be breaking changes that might make some, or all
providers, have minimum Airflow version specified. Change of that minimum supported Airflow version
is a breaking change for provider because installing the new provider might automatically
upgrade Airflow (which might be an undesired side effect of upgrading provider).
* **Airflow Helm Chart**: SemVer rules apply to changes in the chart only. SemVer MAJOR and MINOR
versions for the chart are independent from the Airflow version. We aim to keep backwards
compatibility of the Helm Chart with all released Airflow 2 versions, but some new features might
only work starting from specific Airflow releases. We might however limit the Helm
Chart to depend on minimal Airflow version.
* **Airflow API clients**: SemVer MAJOR and MINOR versions follow MAJOR and MINOR versions of Airflow.
The first MAJOR or MINOR X.Y.0 release of Airflow should always be followed by X.Y.0 release of
all clients. An airflow PATCH X.Y.Z release can be followed by a PATCH release of API clients, only
if this PATCH is relevant to the clients.
The clients then can release their own PATCH releases with bugfixes, independently of Airflow PATCH releases.
As a consequence, each API client will have its own PATCH version that may or may not be in sync with the Airflow
PATCH version. For a specific MAJOR/MINOR Airflow version, users should favor the latest PATCH version of clients
independently of their Airflow PATCH version.
## Version Life Cycle
Apache Airflow version life cycle:
| Version | Current Patch/Minor | State | First Release | Limited Support | EOL/Terminated |
|-----------|-----------------------|-----------|-----------------|-------------------|------------------|
| 2 | 2.5.3 | Supported | Dec 17, 2020 | TBD | TBD |
| 1.10 | 1.10.15 | EOL | Aug 27, 2018 | Dec 17, 2020 | June 17, 2021 |
| 1.9 | 1.9.0 | EOL | Jan 03, 2018 | Aug 27, 2018 | Aug 27, 2018 |
| 1.8 | 1.8.2 | EOL | Mar 19, 2017 | Jan 03, 2018 | Jan 03, 2018 |
| 1.7 | 1.7.1.2 | EOL | Mar 28, 2016 | Mar 19, 2017 | Mar 19, 2017 |
Limited support versions will be supported with security and critical bug fix only.
EOL versions will not get any fixes nor support.
We always recommend that all users run the latest available minor release for whatever major version is in use.
We **highly** recommend upgrading to the latest Airflow major release at the earliest convenient time and before the EOL date.
## Support for Python and Kubernetes versions
As of Airflow 2.0, we agreed to certain rules we follow for Python and Kubernetes support.
They are based on the official release schedule of Python and Kubernetes, nicely summarized in the
[Python Developer's Guide](https://devguide.python.org/#status-of-python-branches) and
[Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/).
1. We drop support for Python and Kubernetes versions when they reach EOL. Except for Kubernetes, a
version stays supported by Airflow if two major cloud providers still provide support for it. We drop
support for those EOL versions in main right after EOL date, and it is effectively removed when we release
the first new MINOR (Or MAJOR if there is no new MINOR version) of Airflow. For example, for Python 3.7 it
means that we will drop support in main right after 27.06.2023, and the first MAJOR or MINOR version of
Airflow released after will not have it.
2. The "oldest" supported version of Python/Kubernetes is the default one until we decide to switch to
later version. "Default" is only meaningful in terms of "smoke tests" in CI PRs, which are run using this
default version and the default reference image available. Currently `apache/airflow:latest`
and `apache/airflow:2.5.3` images are Python 3.7 images. This means that default reference image will
become the default at the time when we start preparing for dropping 3.7 support which is few months
before the end of life for Python 3.7.
3. We support a new version of Python/Kubernetes in main after they are officially released, as soon as we
make them work in our CI pipeline (which might not be immediate due to dependencies catching up with
new versions of Python mostly) we release new images/support in Airflow based on the working CI setup.
## Base OS support for reference Airflow images
The Airflow Community provides conveniently packaged container images that are published whenever
we publish an Apache Airflow release. Those images contain:
* Base OS with necessary packages to install Airflow (stable Debian OS)
* Base Python installation in versions supported at the time of release for the MINOR version of
Airflow released (so there could be different versions for 2.3 and 2.2 line for example)
* Libraries required to connect to suppoerted Databases (again the set of databases supported depends
on the MINOR version of Airflow.
* Predefined set of popular providers (for details see the [Dockerfile](https://raw.githubusercontent.com/apache/airflow/main/Dockerfile)).
* Possibility of building your own, custom image where the user can choose their own set of providers
and libraries (see [Building the image](https://airflow.apache.org/docs/docker-stack/build.html))
* In the future Airflow might also support a "slim" version without providers nor database clients installed
The version of the base OS image is the stable version of Debian. Airflow supports using all currently active
stable versions - as soon as all Airflow dependencies support building, and we set up the CI pipeline for
building and testing the OS version. Approximately 6 months before the end-of-life of a previous stable
version of the OS, Airflow switches the images released to use the latest supported version of the OS.
For example since ``Debian Buster`` end-of-life was August 2022, Airflow switched the images in `main` branch
to use ``Debian Bullseye`` in February/March 2022. The version was used in the next MINOR release after
the switch happened. In case of the Bullseye switch - 2.3.0 version used ``Debian Bullseye``.
The images released in the previous MINOR version continue to use the version that all other releases
for the MINOR version used.
Support for ``Debian Buster`` image was dropped in August 2022 completely and everyone is expected to
stop building their images using ``Debian Buster``.
Users will continue to be able to build their images using stable Debian releases until the end of life and
building and verifying of the images happens in our CI but no unit tests were executed using this image in
the `main` branch.
## Approach to dependencies of Airflow
Airflow has a lot of dependencies - direct and transitive, also Airflow is both - library and application,
therefore our policies to dependencies has to include both - stability of installation of application,
but also ability to install newer version of dependencies for those users who develop DAGs. We developed
the approach where `constraints` are used to make sure airflow can be installed in a repeatable way, while
we do not limit our users to upgrade most of the dependencies. As a result we decided not to upper-bound
version of Airflow dependencies by default, unless we have good reasons to believe upper-bounding them is
needed because of importance of the dependency as well as risk it involves to upgrade specific dependency.
We also upper-bound the dependencies that we know cause problems.
The constraint mechanism of ours takes care about finding and upgrading all the non-upper bound dependencies
automatically (providing that all the tests pass). Our `main` build failures will indicate in case there
are versions of dependencies that break our tests - indicating that we should either upper-bind them or
that we should fix our code/tests to account for the upstream changes from those dependencies.
Whenever we upper-bound such a dependency, we should always comment why we are doing it - i.e. we should have
a good reason why dependency is upper-bound. And we should also mention what is the condition to remove the
binding.
### Approach for dependencies for Airflow Core
Those `extras` and `providers` dependencies are maintained in `setup.cfg`.
There are few dependencies that we decided are important enough to upper-bound them by default, as they are
known to follow predictable versioning scheme, and we know that new versions of those are very likely to
bring breaking changes. We commit to regularly review and attempt to upgrade to the newer versions of
the dependencies as they are released, but this is manual process.
The important dependencies are:
* `SQLAlchemy`: upper-bound to specific MINOR version (SQLAlchemy is known to remove deprecations and
introduce breaking changes especially that support for different Databases varies and changes at
various speed (example: SQLAlchemy 1.4 broke MSSQL integration for Airflow)
* `Alembic`: it is important to handle our migrations in predictable and performant way. It is developed
together with SQLAlchemy. Our experience with Alembic is that it very stable in MINOR version
* `Flask`: We are using Flask as the back-bone of our web UI and API. We know major version of Flask
are very likely to introduce breaking changes across those so limiting it to MAJOR version makes sense
* `werkzeug`: the library is known to cause problems in new versions. It is tightly coupled with Flask
libraries, and we should update them together
* `celery`: Celery is crucial component of Airflow as it used for CeleryExecutor (and similar). Celery
[follows SemVer](https://docs.celeryq.dev/en/stable/contributing.html?highlight=semver#versions), so
we should upper-bound it to the next MAJOR version. Also when we bump the upper version of the library,
we should make sure Celery Provider minimum Airflow version is updated).
* `kubernetes`: Kubernetes is a crucial component of Airflow as it is used for the KubernetesExecutor
(and similar). Kubernetes Python library [follows SemVer](https://github.com/kubernetes-client/python#compatibility),
so we should upper-bound it to the next MAJOR version. Also when we bump the upper version of the library,
we should make sure Kubernetes Provider minimum Airflow version is updated.
### Approach for dependencies in Airflow Providers and extras
Those `extras` and `providers` dependencies are maintained in `provider.yaml` of each provider.
By default, we should not upper-bound dependencies for providers, however each provider's maintainer
might decide to add additional limits (and justify them with comment)
## Release process for Providers
Providers released by the community (with roughly monthly cadence) have
limitation of a minimum supported version of Airflow. The minimum version of
Airflow is the `MINOR` version (2.2, 2.3 etc.) indicating that the providers
might use features that appeared in this release. The default support timespan
for the minimum version of Airflow (there could be justified exceptions) is
that we increase the minimum Airflow version, when 12 months passed since the
first release for the MINOR version of Airflow.
For example this means that by default we upgrade the minimum version of Airflow supported by providers
to 2.4.0 in the first Provider's release after 30th of April 2023. The 30th of April 2022 is the date when the
first `PATCHLEVEL` of 2.3 (2.3.0) has been released.
When we increase the minimum Airflow version, this is not a reason to bump `MAJOR` version of the providers
(unless there are other breaking changes in the provider). The reason for that is that people who use
older version of Airflow will not be able to use that provider (so it is not a breaking change for them)
and for people who are using supported version of Airflow this is not a breaking change on its own - they
will be able to use the new version without breaking their workflows. When we upgraded min-version to
2.2+, our approach was different but as of 2.3+ upgrade (November 2022) we only bump `MINOR` version of the
provider when we increase minimum Airflow version.
Providers are often connected with some stakeholders that are vitally interested in maintaining backwards
compatibilities in their integrations (for example cloud providers, or specific service providers). But,
we are also bound with the [Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html)
which describes who releases, and how to release the ASF software. The provider's governance model is something we name
"mixed governance" - where we follow the release policies, while the burden of maintaining and testing
the cherry-picked versions is on those who commit to perform the cherry-picks and make PRs to older
branches.
The "mixed governance" (optional, per-provider) means that:
* The Airflow Community and release manager decide when to release those providers.
This is fully managed by the community and the usual release-management process following the
[Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html)
* The contributors (who might or might not be direct stakeholders in the provider) will carry the burden
of cherry-picking and testing the older versions of providers.
* There is no "selection" and acceptance process to determine which version of the provider is released.
It is determined by the actions of contributors raising the PR with cherry-picked changes and it follows
the usual PR review process where maintainer approves (or not) and merges (or not) such PR. Simply
speaking - the completed action of cherry-picking and testing the older version of the provider make
it eligible to be released. Unless there is someone who volunteers and perform the cherry-picking and
testing, the provider is not released.
* Branches to raise PR against are created when a contributor commits to perform the cherry-picking
(as a comment in PR to cherry-pick for example)
Usually, community effort is focused on the most recent version of each provider. The community approach is
that we should rather aggressively remove deprecations in "major" versions of the providers - whenever
there is an opportunity to increase major version of a provider, we attempt to remove all deprecations.
However, sometimes there is a contributor (who might or might not represent stakeholder),
willing to make their effort on cherry-picking and testing the non-breaking changes to a selected,
previous major branch of the provider. This results in releasing at most two versions of a
provider at a time:
* potentially breaking "latest" major version
* selected past major version with non-breaking changes applied by the contributor
Cherry-picking such changes follows the same process for releasing Airflow
patch-level releases for a previous minor Airflow version. Usually such cherry-picking is done when
there is an important bugfix and the latest version contains breaking changes that are not
coupled with the bugfix. Releasing them together in the latest version of the provider effectively couples
them, and therefore they're released separately. The cherry-picked changes have to be merged by the committer following the usual rules of the
community.
There is no obligation to cherry-pick and release older versions of the providers.
The community continues to release such older versions of the providers for as long as there is an effort
of the contributors to perform the cherry-picks and carry-on testing of the older provider version.
The availability of stakeholder that can manage "service-oriented" maintenance and agrees to such a
responsibility, will also drive our willingness to accept future, new providers to become community managed.
## Contributing
Want to help build Apache Airflow? Check out our [contributing documentation](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst).
Official Docker (container) images for Apache Airflow are described in [IMAGES.rst](https://github.com/apache/airflow/blob/main/IMAGES.rst).
## Who uses Apache Airflow?
More than 400 organizations are using Apache Airflow
[in the wild](https://github.com/apache/airflow/blob/main/INTHEWILD.md).
## Who Maintains Apache Airflow?
Airflow is the work of the [community](https://github.com/apache/airflow/graphs/contributors),
but the [core committers/maintainers](https://people.apache.org/committers-by-project.html#airflow)
are responsible for reviewing and merging PRs as well as steering conversations around new feature requests.
If you would like to become a maintainer, please review the Apache Airflow
[committer requirements](https://github.com/apache/airflow/blob/main/COMMITTERS.rst#guidelines-to-become-an-airflow-committer).
## Can I use the Apache Airflow logo in my presentation?
Yes! Be sure to abide by the Apache Foundation [trademark policies](https://www.apache.org/foundation/marks/#books) and the Apache Airflow [Brandbook](https://cwiki.apache.org/confluence/display/AIRFLOW/Brandbook). The most up to date logos are found in [this repo](/docs/apache-airflow/img/logos) and on the Apache Software Foundation [website](https://www.apache.org/logos/about.html).
## Airflow merchandise
If you would love to have Apache Airflow stickers, t-shirt, etc. then check out
[Redbubble Shop](https://www.redbubble.com/i/sticker/Apache-Airflow-by-comdev/40497530.EJUG5).
## Links
- [Documentation](https://airflow.apache.org/docs/apache-airflow/stable/)
- [Chat](https://s.apache.org/airflow-slack)
## Sponsors
The CI infrastructure for Apache Airflow has been sponsored by:
%package help
Summary: Development documents and examples for apache-airflow
Provides: python3-apache-airflow-doc
%description help
# Apache Airflow
[](https://badge.fury.io/py/apache-airflow)
[](https://github.com/apache/airflow/actions)
[](https://codecov.io/github/apache/airflow?branch=main)
[](https://www.apache.org/licenses/LICENSE-2.0.txt)
[](https://pypi.org/project/apache-airflow/)
[](https://hub.docker.com/r/apache/airflow)
[](https://hub.docker.com/r/apache/airflow)
[](https://pypi.org/project/apache-airflow/)
[](https://artifacthub.io/packages/search?repo=apache-airflow)
[](https://github.com/psf/black)
[](https://twitter.com/ApacheAirflow)
[](https://s.apache.org/airflow-slack)
[](https://github.com/apache/airflow/graphs/contributors)
[Apache Airflow](https://airflow.apache.org/docs/apache-airflow/stable/) (or simply Airflow) is a platform to programmatically author, schedule, and monitor workflows.
When workflows are defined as code, they become more maintainable, versionable, testable, and collaborative.
Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command line utilities make performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress, and troubleshoot issues when needed.
**Table of contents**
- [Project Focus](#project-focus)
- [Principles](#principles)
- [Requirements](#requirements)
- [Getting started](#getting-started)
- [Installing from PyPI](#installing-from-pypi)
- [Official source code](#official-source-code)
- [Convenience packages](#convenience-packages)
- [User Interface](#user-interface)
- [Semantic versioning](#semantic-versioning)
- [Version Life Cycle](#version-life-cycle)
- [Support for Python and Kubernetes versions](#support-for-python-and-kubernetes-versions)
- [Base OS support for reference Airflow images](#base-os-support-for-reference-airflow-images)
- [Approach to dependencies of Airflow](#approach-to-dependencies-of-airflow)
- [Release process for Providers](#release-process-for-providers)
- [Contributing](#contributing)
- [Who uses Apache Airflow?](#who-uses-apache-airflow)
- [Who Maintains Apache Airflow?](#who-maintains-apache-airflow)
- [Can I use the Apache Airflow logo in my presentation?](#can-i-use-the-apache-airflow-logo-in-my-presentation)
- [Airflow merchandise](#airflow-merchandise)
- [Links](#links)
- [Sponsors](#sponsors)
## Project Focus
Airflow works best with workflows that are mostly static and slowly changing. When the DAG structure is similar from one run to the next, it clarifies the unit of work and continuity. Other similar projects include [Luigi](https://github.com/spotify/luigi), [Oozie](https://oozie.apache.org/) and [Azkaban](https://azkaban.github.io/).
Airflow is commonly used to process data, but has the opinion that tasks should ideally be idempotent (i.e., results of the task will be the same, and will not create duplicated data in a destination system), and should not pass large quantities of data from one task to the next (though tasks can pass metadata using Airflow's [XCom feature](https://airflow.apache.org/docs/apache-airflow/stable/concepts/xcoms.html)). For high-volume, data-intensive tasks, a best practice is to delegate to external services specializing in that type of work.
Airflow is not a streaming solution, but it is often used to process real-time data, pulling data off streams in batches.
## Principles
- **Dynamic**: Airflow pipelines are configuration as code (Python), allowing for dynamic pipeline generation. This allows for writing code that instantiates pipelines dynamically.
- **Extensible**: Easily define your own operators, executors and extend the library so that it fits the level of abstraction that suits your environment.
- **Elegant**: Airflow pipelines are lean and explicit. Parameterizing your scripts is built into the core of Airflow using the powerful **Jinja** templating engine.
- **Scalable**: Airflow has a modular architecture and uses a message queue to orchestrate an arbitrary number of workers.
## Requirements
Apache Airflow is tested with:
| | Main version (dev) | Stable version (2.5.3) |
|---------------------|------------------------------|------------------------------|
| Python | 3.7, 3.8, 3.9, 3.10 | 3.7, 3.8, 3.9, 3.10 |
| Platform | AMD64/ARM64(\*) | AMD64/ARM64(\*) |
| Kubernetes | 1.21, 1.22, 1.23, 1.24, 1.25 | 1.21, 1.22, 1.23, 1.24, 1.25 |
| PostgreSQL | 11, 12, 13, 14, 15 | 11, 12, 13, 14, 15 |
| MySQL | 5.7, 8 | 5.7, 8 |
| SQLite | 3.15.0+ | 3.15.0+ |
| MSSQL | 2017(\*), 2019 (\*) | 2017(\*), 2019 (\*) |
\* Experimental
**Note**: MySQL 5.x versions are unable to or have limitations with
running multiple schedulers -- please see the [Scheduler docs](https://airflow.apache.org/docs/apache-airflow/stable/scheduler.html).
MariaDB is not tested/recommended.
**Note**: SQLite is used in Airflow tests. Do not use it in production. We recommend
using the latest stable version of SQLite for local development.
**Note**: Airflow currently can be run on POSIX-compliant Operating Systems. For development it is regularly
tested on fairly modern Linux Distros and recent versions of MacOS.
On Windows you can run it via WSL2 (Windows Subsystem for Linux 2) or via Linux Containers.
The work to add Windows support is tracked via [#10388](https://github.com/apache/airflow/issues/10388) but
it is not a high priority. You should only use Linux-based distros as "Production" execution environment
as this is the only environment that is supported. The only distro that is used in our CI tests and that
is used in the [Community managed DockerHub image](https://hub.docker.com/p/apache/airflow) is
`Debian Bullseye`.
## Getting started
Visit the official Airflow website documentation (latest **stable** release) for help with
[installing Airflow](https://airflow.apache.org/docs/apache-airflow/stable/installation.html),
[getting started](https://airflow.apache.org/docs/apache-airflow/stable/start.html), or walking
through a more complete [tutorial](https://airflow.apache.org/docs/apache-airflow/stable/tutorial.html).
> Note: If you're looking for documentation for the main branch (latest development branch): you can find it on [s.apache.org/airflow-docs](https://s.apache.org/airflow-docs/).
For more information on Airflow Improvement Proposals (AIPs), visit
the [Airflow Wiki](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals).
Documentation for dependent projects like provider packages, Docker image, Helm Chart, you'll find it in [the documentation index](https://airflow.apache.org/docs/).
## Installing from PyPI
We publish Apache Airflow as `apache-airflow` package in PyPI. Installing it however might be sometimes tricky
because Airflow is a bit of both a library and application. Libraries usually keep their dependencies open, and
applications usually pin them, but we should do neither and both simultaneously. We decided to keep
our dependencies as open as possible (in `setup.py`) so users can install different versions of libraries
if needed. This means that `pip install apache-airflow` will not work from time to time or will
produce unusable Airflow installation.
To have repeatable installation, however, we keep a set of "known-to-be-working" constraint
files in the orphan `constraints-main` and `constraints-2-0` branches. We keep those "known-to-be-working"
constraints files separately per major/minor Python version.
You can use them as constraint files when installing Airflow from PyPI. Note that you have to specify
correct Airflow tag/version/branch and Python versions in the URL.
1. Installing just Airflow:
> Note: Only `pip` installation is currently officially supported.
While it is possible to install Airflow with tools like [Poetry](https://python-poetry.org) or
[pip-tools](https://pypi.org/project/pip-tools), they do not share the same workflow as
`pip` - especially when it comes to constraint vs. requirements management.
Installing via `Poetry` or `pip-tools` is not currently supported.
If you wish to install Airflow using those tools, you should use the constraint files and convert
them to the appropriate format and workflow that your tool requires.
```bash
pip install 'apache-airflow==2.5.3' \
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.5.3/constraints-3.7.txt"
```
2. Installing with extras (i.e., postgres, google)
```bash
pip install 'apache-airflow[postgres,google]==2.5.3' \
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.5.3/constraints-3.7.txt"
```
For information on installing provider packages, check
[providers](http://airflow.apache.org/docs/apache-airflow-providers/index.html).
## Official source code
Apache Airflow is an [Apache Software Foundation](https://www.apache.org) (ASF) project,
and our official source code releases:
- Follow the [ASF Release Policy](https://www.apache.org/legal/release-policy.html)
- Can be downloaded from [the ASF Distribution Directory](https://downloads.apache.org/airflow)
- Are cryptographically signed by the release manager
- Are officially voted on by the PMC members during the
[Release Approval Process](https://www.apache.org/legal/release-policy.html#release-approval)
Following the ASF rules, the source packages released must be sufficient for a user to build and test the
release provided they have access to the appropriate platform and tools.
## Convenience packages
There are other ways of installing and using Airflow. Those are "convenience" methods - they are
not "official releases" as stated by the `ASF Release Policy`, but they can be used by the users
who do not want to build the software themselves.
Those are - in the order of most common ways people install Airflow:
- [PyPI releases](https://pypi.org/project/apache-airflow/) to install Airflow using standard `pip` tool
- [Docker Images](https://hub.docker.com/r/apache/airflow) to install airflow via
`docker` tool, use them in Kubernetes, Helm Charts, `docker-compose`, `docker swarm`, etc. You can
read more about using, customising, and extending the images in the
[Latest docs](https://airflow.apache.org/docs/docker-stack/index.html), and
learn details on the internals in the [IMAGES.rst](https://github.com/apache/airflow/blob/main/IMAGES.rst) document.
- [Tags in GitHub](https://github.com/apache/airflow/tags) to retrieve the git project sources that
were used to generate official source packages via git
All those artifacts are not official releases, but they are prepared using officially released sources.
Some of those artifacts are "development" or "pre-release" ones, and they are clearly marked as such
following the ASF Policy.
## User Interface
- **DAGs**: Overview of all DAGs in your environment.
- **Grid**: Grid representation of a DAG that spans across time.
- **Graph**: Visualization of a DAG's dependencies and their current status for a specific run.
- **Task Duration**: Total time spent on different tasks over time.
- **Gantt**: Duration and overlap of a DAG.
- **Code**: Quick way to view source code of a DAG.
## Semantic versioning
As of Airflow 2.0.0, we support a strict [SemVer](https://semver.org/) approach for all packages released.
There are few specific rules that we agreed to that define details of versioning of the different
packages:
* **Airflow**: SemVer rules apply to core airflow only (excludes any changes to providers).
Changing limits for versions of Airflow dependencies is not a breaking change on its own.
* **Airflow Providers**: SemVer rules apply to changes in the particular provider's code only.
SemVer MAJOR and MINOR versions for the packages are independent of the Airflow version.
For example, `google 4.1.0` and `amazon 3.0.3` providers can happily be installed
with `Airflow 2.1.2`. If there are limits of cross-dependencies between providers and Airflow packages,
they are present in providers as `install_requires` limitations. We aim to keep backwards
compatibility of providers with all previously released Airflow 2 versions but
there will sometimes be breaking changes that might make some, or all
providers, have minimum Airflow version specified. Change of that minimum supported Airflow version
is a breaking change for provider because installing the new provider might automatically
upgrade Airflow (which might be an undesired side effect of upgrading provider).
* **Airflow Helm Chart**: SemVer rules apply to changes in the chart only. SemVer MAJOR and MINOR
versions for the chart are independent from the Airflow version. We aim to keep backwards
compatibility of the Helm Chart with all released Airflow 2 versions, but some new features might
only work starting from specific Airflow releases. We might however limit the Helm
Chart to depend on minimal Airflow version.
* **Airflow API clients**: SemVer MAJOR and MINOR versions follow MAJOR and MINOR versions of Airflow.
The first MAJOR or MINOR X.Y.0 release of Airflow should always be followed by X.Y.0 release of
all clients. An airflow PATCH X.Y.Z release can be followed by a PATCH release of API clients, only
if this PATCH is relevant to the clients.
The clients then can release their own PATCH releases with bugfixes, independently of Airflow PATCH releases.
As a consequence, each API client will have its own PATCH version that may or may not be in sync with the Airflow
PATCH version. For a specific MAJOR/MINOR Airflow version, users should favor the latest PATCH version of clients
independently of their Airflow PATCH version.
## Version Life Cycle
Apache Airflow version life cycle:
| Version | Current Patch/Minor | State | First Release | Limited Support | EOL/Terminated |
|-----------|-----------------------|-----------|-----------------|-------------------|------------------|
| 2 | 2.5.3 | Supported | Dec 17, 2020 | TBD | TBD |
| 1.10 | 1.10.15 | EOL | Aug 27, 2018 | Dec 17, 2020 | June 17, 2021 |
| 1.9 | 1.9.0 | EOL | Jan 03, 2018 | Aug 27, 2018 | Aug 27, 2018 |
| 1.8 | 1.8.2 | EOL | Mar 19, 2017 | Jan 03, 2018 | Jan 03, 2018 |
| 1.7 | 1.7.1.2 | EOL | Mar 28, 2016 | Mar 19, 2017 | Mar 19, 2017 |
Limited support versions will be supported with security and critical bug fix only.
EOL versions will not get any fixes nor support.
We always recommend that all users run the latest available minor release for whatever major version is in use.
We **highly** recommend upgrading to the latest Airflow major release at the earliest convenient time and before the EOL date.
## Support for Python and Kubernetes versions
As of Airflow 2.0, we agreed to certain rules we follow for Python and Kubernetes support.
They are based on the official release schedule of Python and Kubernetes, nicely summarized in the
[Python Developer's Guide](https://devguide.python.org/#status-of-python-branches) and
[Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/).
1. We drop support for Python and Kubernetes versions when they reach EOL. Except for Kubernetes, a
version stays supported by Airflow if two major cloud providers still provide support for it. We drop
support for those EOL versions in main right after EOL date, and it is effectively removed when we release
the first new MINOR (Or MAJOR if there is no new MINOR version) of Airflow. For example, for Python 3.7 it
means that we will drop support in main right after 27.06.2023, and the first MAJOR or MINOR version of
Airflow released after will not have it.
2. The "oldest" supported version of Python/Kubernetes is the default one until we decide to switch to
later version. "Default" is only meaningful in terms of "smoke tests" in CI PRs, which are run using this
default version and the default reference image available. Currently `apache/airflow:latest`
and `apache/airflow:2.5.3` images are Python 3.7 images. This means that default reference image will
become the default at the time when we start preparing for dropping 3.7 support which is few months
before the end of life for Python 3.7.
3. We support a new version of Python/Kubernetes in main after they are officially released, as soon as we
make them work in our CI pipeline (which might not be immediate due to dependencies catching up with
new versions of Python mostly) we release new images/support in Airflow based on the working CI setup.
## Base OS support for reference Airflow images
The Airflow Community provides conveniently packaged container images that are published whenever
we publish an Apache Airflow release. Those images contain:
* Base OS with necessary packages to install Airflow (stable Debian OS)
* Base Python installation in versions supported at the time of release for the MINOR version of
Airflow released (so there could be different versions for 2.3 and 2.2 line for example)
* Libraries required to connect to suppoerted Databases (again the set of databases supported depends
on the MINOR version of Airflow.
* Predefined set of popular providers (for details see the [Dockerfile](https://raw.githubusercontent.com/apache/airflow/main/Dockerfile)).
* Possibility of building your own, custom image where the user can choose their own set of providers
and libraries (see [Building the image](https://airflow.apache.org/docs/docker-stack/build.html))
* In the future Airflow might also support a "slim" version without providers nor database clients installed
The version of the base OS image is the stable version of Debian. Airflow supports using all currently active
stable versions - as soon as all Airflow dependencies support building, and we set up the CI pipeline for
building and testing the OS version. Approximately 6 months before the end-of-life of a previous stable
version of the OS, Airflow switches the images released to use the latest supported version of the OS.
For example since ``Debian Buster`` end-of-life was August 2022, Airflow switched the images in `main` branch
to use ``Debian Bullseye`` in February/March 2022. The version was used in the next MINOR release after
the switch happened. In case of the Bullseye switch - 2.3.0 version used ``Debian Bullseye``.
The images released in the previous MINOR version continue to use the version that all other releases
for the MINOR version used.
Support for ``Debian Buster`` image was dropped in August 2022 completely and everyone is expected to
stop building their images using ``Debian Buster``.
Users will continue to be able to build their images using stable Debian releases until the end of life and
building and verifying of the images happens in our CI but no unit tests were executed using this image in
the `main` branch.
## Approach to dependencies of Airflow
Airflow has a lot of dependencies - direct and transitive, also Airflow is both - library and application,
therefore our policies to dependencies has to include both - stability of installation of application,
but also ability to install newer version of dependencies for those users who develop DAGs. We developed
the approach where `constraints` are used to make sure airflow can be installed in a repeatable way, while
we do not limit our users to upgrade most of the dependencies. As a result we decided not to upper-bound
version of Airflow dependencies by default, unless we have good reasons to believe upper-bounding them is
needed because of importance of the dependency as well as risk it involves to upgrade specific dependency.
We also upper-bound the dependencies that we know cause problems.
The constraint mechanism of ours takes care about finding and upgrading all the non-upper bound dependencies
automatically (providing that all the tests pass). Our `main` build failures will indicate in case there
are versions of dependencies that break our tests - indicating that we should either upper-bind them or
that we should fix our code/tests to account for the upstream changes from those dependencies.
Whenever we upper-bound such a dependency, we should always comment why we are doing it - i.e. we should have
a good reason why dependency is upper-bound. And we should also mention what is the condition to remove the
binding.
### Approach for dependencies for Airflow Core
Those `extras` and `providers` dependencies are maintained in `setup.cfg`.
There are few dependencies that we decided are important enough to upper-bound them by default, as they are
known to follow predictable versioning scheme, and we know that new versions of those are very likely to
bring breaking changes. We commit to regularly review and attempt to upgrade to the newer versions of
the dependencies as they are released, but this is manual process.
The important dependencies are:
* `SQLAlchemy`: upper-bound to specific MINOR version (SQLAlchemy is known to remove deprecations and
introduce breaking changes especially that support for different Databases varies and changes at
various speed (example: SQLAlchemy 1.4 broke MSSQL integration for Airflow)
* `Alembic`: it is important to handle our migrations in predictable and performant way. It is developed
together with SQLAlchemy. Our experience with Alembic is that it very stable in MINOR version
* `Flask`: We are using Flask as the back-bone of our web UI and API. We know major version of Flask
are very likely to introduce breaking changes across those so limiting it to MAJOR version makes sense
* `werkzeug`: the library is known to cause problems in new versions. It is tightly coupled with Flask
libraries, and we should update them together
* `celery`: Celery is crucial component of Airflow as it used for CeleryExecutor (and similar). Celery
[follows SemVer](https://docs.celeryq.dev/en/stable/contributing.html?highlight=semver#versions), so
we should upper-bound it to the next MAJOR version. Also when we bump the upper version of the library,
we should make sure Celery Provider minimum Airflow version is updated).
* `kubernetes`: Kubernetes is a crucial component of Airflow as it is used for the KubernetesExecutor
(and similar). Kubernetes Python library [follows SemVer](https://github.com/kubernetes-client/python#compatibility),
so we should upper-bound it to the next MAJOR version. Also when we bump the upper version of the library,
we should make sure Kubernetes Provider minimum Airflow version is updated.
### Approach for dependencies in Airflow Providers and extras
Those `extras` and `providers` dependencies are maintained in `provider.yaml` of each provider.
By default, we should not upper-bound dependencies for providers, however each provider's maintainer
might decide to add additional limits (and justify them with comment)
## Release process for Providers
Providers released by the community (with roughly monthly cadence) have
limitation of a minimum supported version of Airflow. The minimum version of
Airflow is the `MINOR` version (2.2, 2.3 etc.) indicating that the providers
might use features that appeared in this release. The default support timespan
for the minimum version of Airflow (there could be justified exceptions) is
that we increase the minimum Airflow version, when 12 months passed since the
first release for the MINOR version of Airflow.
For example this means that by default we upgrade the minimum version of Airflow supported by providers
to 2.4.0 in the first Provider's release after 30th of April 2023. The 30th of April 2022 is the date when the
first `PATCHLEVEL` of 2.3 (2.3.0) has been released.
When we increase the minimum Airflow version, this is not a reason to bump `MAJOR` version of the providers
(unless there are other breaking changes in the provider). The reason for that is that people who use
older version of Airflow will not be able to use that provider (so it is not a breaking change for them)
and for people who are using supported version of Airflow this is not a breaking change on its own - they
will be able to use the new version without breaking their workflows. When we upgraded min-version to
2.2+, our approach was different but as of 2.3+ upgrade (November 2022) we only bump `MINOR` version of the
provider when we increase minimum Airflow version.
Providers are often connected with some stakeholders that are vitally interested in maintaining backwards
compatibilities in their integrations (for example cloud providers, or specific service providers). But,
we are also bound with the [Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html)
which describes who releases, and how to release the ASF software. The provider's governance model is something we name
"mixed governance" - where we follow the release policies, while the burden of maintaining and testing
the cherry-picked versions is on those who commit to perform the cherry-picks and make PRs to older
branches.
The "mixed governance" (optional, per-provider) means that:
* The Airflow Community and release manager decide when to release those providers.
This is fully managed by the community and the usual release-management process following the
[Apache Software Foundation release policy](https://www.apache.org/legal/release-policy.html)
* The contributors (who might or might not be direct stakeholders in the provider) will carry the burden
of cherry-picking and testing the older versions of providers.
* There is no "selection" and acceptance process to determine which version of the provider is released.
It is determined by the actions of contributors raising the PR with cherry-picked changes and it follows
the usual PR review process where maintainer approves (or not) and merges (or not) such PR. Simply
speaking - the completed action of cherry-picking and testing the older version of the provider make
it eligible to be released. Unless there is someone who volunteers and perform the cherry-picking and
testing, the provider is not released.
* Branches to raise PR against are created when a contributor commits to perform the cherry-picking
(as a comment in PR to cherry-pick for example)
Usually, community effort is focused on the most recent version of each provider. The community approach is
that we should rather aggressively remove deprecations in "major" versions of the providers - whenever
there is an opportunity to increase major version of a provider, we attempt to remove all deprecations.
However, sometimes there is a contributor (who might or might not represent stakeholder),
willing to make their effort on cherry-picking and testing the non-breaking changes to a selected,
previous major branch of the provider. This results in releasing at most two versions of a
provider at a time:
* potentially breaking "latest" major version
* selected past major version with non-breaking changes applied by the contributor
Cherry-picking such changes follows the same process for releasing Airflow
patch-level releases for a previous minor Airflow version. Usually such cherry-picking is done when
there is an important bugfix and the latest version contains breaking changes that are not
coupled with the bugfix. Releasing them together in the latest version of the provider effectively couples
them, and therefore they're released separately. The cherry-picked changes have to be merged by the committer following the usual rules of the
community.
There is no obligation to cherry-pick and release older versions of the providers.
The community continues to release such older versions of the providers for as long as there is an effort
of the contributors to perform the cherry-picks and carry-on testing of the older provider version.
The availability of stakeholder that can manage "service-oriented" maintenance and agrees to such a
responsibility, will also drive our willingness to accept future, new providers to become community managed.
## Contributing
Want to help build Apache Airflow? Check out our [contributing documentation](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst).
Official Docker (container) images for Apache Airflow are described in [IMAGES.rst](https://github.com/apache/airflow/blob/main/IMAGES.rst).
## Who uses Apache Airflow?
More than 400 organizations are using Apache Airflow
[in the wild](https://github.com/apache/airflow/blob/main/INTHEWILD.md).
## Who Maintains Apache Airflow?
Airflow is the work of the [community](https://github.com/apache/airflow/graphs/contributors),
but the [core committers/maintainers](https://people.apache.org/committers-by-project.html#airflow)
are responsible for reviewing and merging PRs as well as steering conversations around new feature requests.
If you would like to become a maintainer, please review the Apache Airflow
[committer requirements](https://github.com/apache/airflow/blob/main/COMMITTERS.rst#guidelines-to-become-an-airflow-committer).
## Can I use the Apache Airflow logo in my presentation?
Yes! Be sure to abide by the Apache Foundation [trademark policies](https://www.apache.org/foundation/marks/#books) and the Apache Airflow [Brandbook](https://cwiki.apache.org/confluence/display/AIRFLOW/Brandbook). The most up to date logos are found in [this repo](/docs/apache-airflow/img/logos) and on the Apache Software Foundation [website](https://www.apache.org/logos/about.html).
## Airflow merchandise
If you would love to have Apache Airflow stickers, t-shirt, etc. then check out
[Redbubble Shop](https://www.redbubble.com/i/sticker/Apache-Airflow-by-comdev/40497530.EJUG5).
## Links
- [Documentation](https://airflow.apache.org/docs/apache-airflow/stable/)
- [Chat](https://s.apache.org/airflow-slack)
## Sponsors
The CI infrastructure for Apache Airflow has been sponsored by:
%prep
%autosetup -n apache-airflow-2.5.3
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-apache-airflow -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri Apr 21 2023 Python_Bot - 2.5.3-1
- Package Spec generated