Package apache-airflow-providers-edge3
Release: 5.1.0
Handle edge workers on remote sites via HTTP(s) connection and orchestrates work over distributed sites.
When tasks need to be executed on remote sites where the connection need to pass through firewalls or other network restrictions, the Edge Worker can be deployed. The Edge Worker is a lightweight process with reduced dependencies. The worker only needs to be able to communicate with the central Airflow site via HTTPS.
In the central Airflow site the EdgeExecutor is used to orchestrate the work. The EdgeExecutor is a custom executor which is used to schedule tasks on the edge workers. The EdgeExecutor can co-exist with other executors (for example CeleryExecutor or KubernetesExecutor) in the same Airflow site.
Additional REST API endpoints are provided to distribute tasks and manage the edge workers. The endpoints are provided by the API server.
Provider package
This is a provider package for edge3 provider. All classes for this provider package are in airflow.providers.edge3 python package.
You can find package information and changelog for the provider in the documentation.
Installation
You can install this package on top of an existing Airflow installation (see Requirements below for the minimum Airflow version supported) via pip install apache-airflow-providers-edge3
The package supports the following python versions: 3.11,3.12,3.13,3.14
Requirements
PIP package |
Version required |
|---|---|
apache-airflow |
>=3.0.0,!=3.1.0 |
apache-airflow-providers-common-compat |
>=1.15.0 |
pydantic |
>=2.11.0 |
retryhttp |
>=1.4.0 |
aiofiles |
>=23.2.0 |
aiohttp |
>=3.14.0 |
The changelog for the provider package can be found in the changelog.
Metadata
Release files for apache-airflow-providers-edge3 5.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| apache_airflow_providers_edge3-5.1.0.tar.gz | 719.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apache_airflow_providers_edge3-5.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / apache_airflow_providers_edge3-5.1.0.tar.gz
| Download URL | apache_airflow_providers_edge3-5.1.0.tar.gz |
|---|---|
| Size | 719.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
125921c1765990e55fdee0d72eb501e8cd318d550e3fe1203d0f4a2bf6297e43
|
|
BLAKE2b-256 checksum How to use checksums |
c0abb63dc078ee1d58e4f00a801e38c070acf04e8ce921fec1581f8783d9b725
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.5
|
Release files / apache_airflow_providers_edge3-5.1.0-py3-none-any.whl
| Download URL | apache_airflow_providers_edge3-5.1.0-py3-none-any.whl |
|---|---|
| Size | 484.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d0e3c7790aa919c33db93c85b9cd7a4142d5405ba9b5d1cbe7ee1f5600c7182
|
|
BLAKE2b-256 checksum How to use checksums |
b7c0bc6a63c7057b032cf69edaf10246269cefd11ce2d3d02883e1eeb3728d5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.5
|
Security for apache-airflow-providers-edge3 5.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
