airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sampath (Jira)" <j...@apache.org>
Subject [jira] [Updated] (AIRFLOW-5564) Feature Request to validate Airflow Connection Hook from UI
Date Fri, 27 Sep 2019 10:19:00 GMT

     [ https://issues.apache.org/jira/browse/AIRFLOW-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sampath updated AIRFLOW-5564:
-----------------------------
    Description: 
Feature Request to validate Airflow Connection Hook from UI, just like mysql workbench lets
you test if a mysql connection is valid or not before saving.

In a realtime scenario(airflow (webserver & scheduler) & 2-4 celery worker nodes) for
each airflow hook, at each worker node and in each environment we had to this test.

In future as we grow, there will be more connection hooks & this will keep increase our
workload of simple yet repetitive works.

So requesting following
 # *Airflow Connection Hooks* should have an option to validate them. At least for simple
hooks like SSH & Mysql.
 # These tests should happen on each (Celery) *Worker* node.

Since airflow uses paramiko, sqlachemy internally(I think) this problem can be quickly solvable
for SSH & Mysql Hooks(starting point). If there any development happening in this area,
kindly please point me there & then close this request.

  was:
Feature Request to validate Airflow Connection Hook from UI, just like mysql workbench lets
you test is a mysql connection is valid or not before saving.

In a realtime scenario(airflow(master & scheduler) & 2-4 celery worker nodes) for
each airflow hook, at each worker node and in each environment we had to this test.

In future as we grow, there will be more connection hooks & this will increase our workload
of simple yet repetitive works.

So requesting following
 # *Airflow Connection Hooks* should have an option to validate them. At least for simple
hooks like SSH & Mysql.
 # These tests should happen on each (Celery) *Worker* node.

Since airflow uses paramiko, sqlachemy internally(I think) this problem can be quickly solvable
for SSH & Mysql Hooks(starting point). If there any development happening in this area,
kindly please point me there & then close this request.


> Feature Request to validate Airflow Connection Hook from UI
> -----------------------------------------------------------
>
>                 Key: AIRFLOW-5564
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5564
>             Project: Apache Airflow
>          Issue Type: Wish
>          Components: celery, webserver, worker
>    Affects Versions: 1.10.2
>            Reporter: Sampath
>            Priority: Major
>
> Feature Request to validate Airflow Connection Hook from UI, just like mysql workbench
lets you test if a mysql connection is valid or not before saving.
> In a realtime scenario(airflow (webserver & scheduler) & 2-4 celery worker nodes) for
each airflow hook, at each worker node and in each environment we had to this test.
> In future as we grow, there will be more connection hooks & this will keep increase
our workload of simple yet repetitive works.
> So requesting following
>  # *Airflow Connection Hooks* should have an option to validate them. At least for simple
hooks like SSH & Mysql.
>  # These tests should happen on each (Celery) *Worker* node.
> Since airflow uses paramiko, sqlachemy internally(I think) this problem can be quickly
solvable for SSH & Mysql Hooks(starting point). If there any development happening in
this area, kindly please point me there & then close this request.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message