You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want users to be able to easily setup/register a given DAG "instance", from their given DeepLynx container. They'll need to provide some configuration and authentication info, and have that stored somewhere and be accessible to both Airflow and DeepLynx.
Design
I think most of that info can be stored in Airflow's Connection object. If so, we'll need to decide the exact backend we use for that. We could go with a standard Airflow approach of storing our Connections in a table in our Airflow metadata database. If we go that route, we could have our Connections table stored in a Postgres DB, and give access to both Airflow and DeepLynx.
The text was updated successfully, but these errors were encountered:
Reason
We want users to be able to easily setup/register a given DAG "instance", from their given DeepLynx container. They'll need to provide some configuration and authentication info, and have that stored somewhere and be accessible to both Airflow and DeepLynx.
Design
I think most of that info can be stored in Airflow's Connection object. If so, we'll need to decide the exact backend we use for that. We could go with a standard Airflow approach of storing our Connections in a table in our Airflow metadata database. If we go that route, we could have our Connections table stored in a Postgres DB, and give access to both Airflow and DeepLynx.
The text was updated successfully, but these errors were encountered: