From dev-return-8766-archive-asf-public=cust-asf.ponee.io@airflow.apache.org Wed Jun 26 10:25:58 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 2D7BF18064D for ; Wed, 26 Jun 2019 12:25:58 +0200 (CEST) Received: (qmail 9936 invoked by uid 500); 26 Jun 2019 10:25:56 -0000 Mailing-List: contact dev-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 dev@airflow.apache.org Received: (qmail 9924 invoked by uid 99); 26 Jun 2019 10:25:56 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Jun 2019 10:25:56 +0000 Received: from themisto-2.localdomain (231.25.169.217.in-addr.arpa [217.169.25.231]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 74B685807; Wed, 26 Jun 2019 10:25:52 +0000 (UTC) From: Ash Berlin-Taylor Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Field "owner" in DAG Model Date: Wed, 26 Jun 2019 11:25:50 +0100 References: <1phsdJzYEfLLi62NlsKFSBBeH6E0V154EZdU883oeC4YkKDjGB1lI9hAex-DqzZRfq1I747Dwl9iYWwF2Lw3dpk0wmIUulVazE2ipIAFo-Y=@protonmail.com> To: dev@airflow.apache.org, airflowuser In-Reply-To: <1phsdJzYEfLLi62NlsKFSBBeH6E0V154EZdU883oeC4YkKDjGB1lI9hAex-DqzZRfq1I747Dwl9iYWwF2Lw3dpk0wmIUulVazE2ipIAFo-Y=@protonmail.com> Message-Id: <3F112942-E4C7-43E4-A0BE-B5D49FC991EB@apache.org> X-Mailer: Apple Mail (2.3445.104.11) That was broken in 1.10.3 - should be fixed in .4 > On 26 Jun 2019, at 11:00, airflowuser = wrote: >=20 > If I may ask... > in the Old UI how do you filter DAGs by owner? > I'm running 1.10.3 and in the Search bar it searches only DAG it = doesn't search by owner. >=20 >=20 > Sent with ProtonMail Secure Email. >=20 > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 > On Wednesday, June 26, 2019 12:27 PM, Deng Xiaodong = wrote: >=20 >> Hi folks, >>=20 >> In DAG Model, we have "owner" field. In earlier Flask-Admin based UI = (which >> is already removed in master branch), it was used by "filter_by_user" >> config item in [webserver] section to help control access. But now = seems >> it's not used anywhere already (correct me if I'm wrong). >>=20 >> I would like to understand from the community: shall we remove this = field? >> Or there can be other usage on this field? >>=20 >> One use case I have in mind is to use "owner" to enhance DAG-level = access >> control. Currently the DAG-level access control is implemented by = creating >> a new permission for each DAG, which may be "tedious" to manage if = there >> are many DAGs. We may use "owner" to group DAGs, so we can create new >> permission for each "owner" rather than creating new permission for = each >> single DAG. >>=20 >> Please share your thoughts. Thanks. >>=20 >> Best regards, >>=20 >> XD >=20 >=20