Installing Providers from Sources¶
Released packages¶
Airbyte
Alibaba
Amazon
Apache Beam
Apache Cassandra
Apache Drill
Apache Druid
Apache Flink
Apache HDFS
Apache Hive
Apache Iceberg
Apache Impala
Apache Kafka
Apache Kylin
Apache Livy
Apache Pig
Apache Pinot
Apache Spark
Apprise
ArangoDB
Asana
Atlassian Jira
Celery
IBM Cloudant
Kubernetes
Cohere
Common Compat
Common IO
Common SQL
Databricks
Datadog
dbt Cloud
Dingding
Discord
Docker
Edge Executor
Elasticsearch
Exasol
Fab
Facebook
File Transfer Protocol (FTP)
Github
Google
gRPC
Hashicorp
Hypertext Transfer Protocol (HTTP)
Internet Message Access Protocol (IMAP)
Influxdb
Java Database Connectivity (JDBC)
Jenkins
Microsoft Azure
Microsoft SQL Server (MSSQL)
PowerShell Remoting Protocol (PSRP)
Windows Remote Management (WinRM)
MongoDB
MySQL
Neo4j
ODBC
OpenAI
OpenFaaS
OpenLineage Airflow
OpenSearch
Opsgenie
Oracle
Pagerduty
Papermill
pgvector
Pinecone
PostgreSQL
Presto
Qdrant
Redis
Salesforce
Samba
Segment
Sendgrid
SFTP
Singularity
Slack
Simple Mail Transfer Protocol (SMTP)
Snowflake
SQLite
SSH
Standard
Tableau
Telegram
Teradata
Trino
Vertica
Weaviate
Yandex
YDB
Zendesk
You can also install Apache Airflow Providers
- as most Python packages - via PyPI.
You can choose different version of Airflow by selecting different version from the drop-down at
the top-left of the page.
Release integrity¶
It is essential that you verify the integrity of the downloaded files using the PGP or SHA signatures. The PGP signatures can be verified using GPG or PGP. Please download the KEYS as well as the asc signature files for relevant distribution. It is recommended to get these files from the main distribution directory and not from the mirrors.
gpg -i KEYS
or
pgpk -a KEYS
or
pgp -ka KEYS
To verify the binaries/sources you can download the relevant asc files for it from main distribution directory and follow the below guide.
gpg --verify apache-airflow-providers-********.asc apache-airflow-providers-*********
or
pgpv apache-airflow-providers-********.asc
or
pgp apache-airflow-providers-********.asc
Example:
$ gpg --verify apache-airflow-providers-airbyte-1.0.0-source.tar.gz.asc apache-airflow-providers-airbyte-1.0.0-source.tar.gz
gpg: Signature made Sat 11 Sep 12:49:54 2021 BST
gpg: using RSA key CDE15C6E4D3A8EC4ECF4BA4B6674E08AD7DE406F
gpg: issuer "kaxilnaik@apache.org"
gpg: Good signature from "Kaxil Naik <kaxilnaik@apache.org>" [unknown]
gpg: aka "Kaxil Naik <kaxilnaik@gmail.com>" [unknown]
gpg: WARNING: The key's User ID is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: CDE1 5C6E 4D3A 8EC4 ECF4 BA4B 6674 E08A D7DE 406F
The “Good signature from …” is indication that the signatures are correct.
Do not worry about the “not certified with a trusted signature” warning. Most of the certificates used
by release managers are self signed, that’s why you get this warning. By importing the server in the
previous step and importing it via ID from KEYS
page, you know that this is a valid Key already.
For SHA512 sum check, download the relevant sha512
and run the following:
shasum -a 512 apache-airflow-providers-******** | diff - apache-airflow-providers-********.sha512
The SHASUM
of the file should match the one provided in .sha512
file.
Example:
shasum -a 512 apache-airflow-providers-airbyte-1.0.0-source.tar.gz | diff - apache-airflow-providers-airbyte-1.0.0-source.tar.gz.sha512