From commits-return-68075-archive-asf-public=cust-asf.ponee.io@airflow.apache.org Fri Sep 27 10:19:08 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 2B825180638 for ; Fri, 27 Sep 2019 12:19:08 +0200 (CEST) Received: (qmail 15749 invoked by uid 500); 27 Sep 2019 10:19:07 -0000 Mailing-List: contact commits-help@airflow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.apache.org Delivered-To: mailing list commits@airflow.apache.org Received: (qmail 15740 invoked by uid 99); 27 Sep 2019 10:19:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Sep 2019 10:19:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 03512C03DD for ; Fri, 27 Sep 2019 10:19:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -113 X-Spam-Level: X-Spam-Status: No, score=-113 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 9LbiWhgD5zOw for ; Fri, 27 Sep 2019 10:19:04 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=207.244.88.153; helo=mail.apache.org; envelope-from=jira@apache.org; receiver= Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with SMTP id EFEB37F642 for ; Fri, 27 Sep 2019 10:19:03 +0000 (UTC) Received: (qmail 14887 invoked by uid 99); 27 Sep 2019 10:19:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Sep 2019 10:19:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E600AE2CE6 for ; Fri, 27 Sep 2019 10:19:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 0BA3E7802BE for ; Fri, 27 Sep 2019 10:19:00 +0000 (UTC) Date: Fri, 27 Sep 2019 10:19:00 +0000 (UTC) From: "Sampath (Jira)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRFLOW-5564) Feature Request to validate Airflow Connection Hook from UI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRFLOW-5564?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sampath updated AIRFLOW-5564: ----------------------------- Description:=20 Feature Request to validate Airflow Connection Hook from UI, just like mysq= l workbench lets you test if a mysql connection is valid or not before savi= ng. In a realtime scenario(airflow (webserver & scheduler) & 2-4 celery worker = nodes)=C2=A0for each airflow=C2=A0hook, at each worker node and in each env= ironment 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 le= ast 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 de= velopment 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 mysq= l workbench lets you test is a mysql connection is valid or not before savi= ng. In a realtime scenario(airflow(master & scheduler) & 2-4 celery worker node= s)=C2=A0for each airflow=C2=A0hook, at each worker node and in each environ= ment we had to this test. In future as we grow, there will be more connection hooks & this will incre= ase our workload of simple yet repetitive works. So requesting following # *Airflow Connection Hooks* should have an option to validate them. At le= ast 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 de= velopment 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 my= sql workbench lets you test if a mysql connection is valid or not before sa= ving. > In a realtime scenario(airflow (webserver & scheduler) & 2-4 celery worke= r nodes)=C2=A0for each airflow=C2=A0hook, at each worker node and in each e= nvironment we had to this test. > In future as we grow, there will be more connection hooks & this will kee= p 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 c= an be quickly solvable for SSH & Mysql Hooks(starting point). If there any = development happening in this area, kindly please point me there & then clo= se this request. -- This message was sent by Atlassian Jira (v8.3.4#803005)