pyAirbyte in air gapped environment #400
-
Trying to use Airflow & pyAirbyte to extract data from an internal API to an postgresql cache using docker containers. On my local machine it works fine, I build my container, do an pip install and everything is nice and dandy. However, it seems that the first time the image is used, it fetches some things from the repo, and when deploying the image in our air gapped environment this does not work. How do I install neccessary things beforehand to be able to use my custom API-source yaml generated by Airbyte builder? The URl that times out is: https://connectors.airbyte.com/files/registries/v0/oss_registry.json Or is it just built in to connect to the URI no matter what? Is it possible to disable? I thougt "install_if_missing=False" would fix this. My source def in Airflow:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Answer myself here. Digging through the python code, I found the logic that checks the registry. The code have an built in feature to look at an local file if an environment variable was set, so one can get around this. I pulled the URL to an json-file, and added the environment variable to my airflow stack:
And hey presto! It works! |
Beta Was this translation helpful? Give feedback.
Answer myself here. Digging through the python code, I found the logic that checks the registry. The code have an built in feature to look at an local file if an environment variable was set, so one can get around this. I pulled the URL to an json-file, and added the environment variable to my airflow stack:
AIRBYTE_LOCAL_REGISTRY: '/filepath/oss-registry.json'
And hey presto! It works!