-
python3-apache-airflow-providers-facebook-3.7.0-1.lbn36.noarch
Package apache-airflow-providers-facebook
Facebook Ads
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-ftp-3.12.2-1.lbn36.noarch
Package apache-airflow-providers-ftp
File Transfer Protocol (FTP)
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-github-2.8.2-1.lbn36.noarch
Package apache-airflow-providers-github
GitHub
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-google-14.0.0-1.lbn36.noarch
Package apache-airflow-providers-google
Google services including:
Google Ads
Google Cloud (GCP)
Google Firebase
Google LevelDB
Google Marketing Platform
Google Workspace (formerly Google Suite)
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-grpc-3.7.2-1.lbn36.noarch
Package apache-airflow-providers-grpc
gRPC
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-hashicorp-4.0.0-1.lbn36.noarch
Package apache-airflow-providers-hashicorp
Hashicorp including Hashicorp Vault
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-http-5.2.0-1.lbn36.noarch
Package apache-airflow-providers-http
Hypertext Transfer Protocol (HTTP)
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-imap-3.8.2-1.lbn36.noarch
Package apache-airflow-providers-imap
Internet Message Access Protocol (IMAP)
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-influxdb-2.8.2-1.lbn36.noarch
Package apache-airflow-providers-influxdb
InfluxDB
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
-
python3-apache-airflow-providers-isolation-1.0.1-1.lbn36.noarch
Isolation Provider
Runtime Operator Isolation in Airflow.
Created with ❤️ by the CSE Team @ Astronomer
The Isolation Provider provides the IsolatedOperator and the isolationctl CLI.
It provides the capacity to run any Airflow Operator in an isolated fashion.
Why use IsolatedOperator?
Run a different version of an underlying library,
between separate teams on the same Airflow instance,
even between separate tasks in the same DAG
Run entirely separate versions of Python for a task
Keep "heavy" dependencies separate from Airflow
Run an Airflow task in a completely separate environment - or on a server all the way across the world.
Run a task "safely" - separate from the Airflow instance
Run a task with dependencies that conflict more easily
Do all of the above while having unmodified access to (almost) all of 'no
Located in
LBN
/
…
/
Data Science
/
BastionLinux 36
