API & CLI Permission Checking

2020-08-05 Thread Ace Haidrey
Hi all, I wanted to ask you a question, if you knew the answer. The cli and api currently in upstream doesn’t have any support for doing RBAC role checking on if a user can actually trigger a dag (if they have the perms) or things of that sort from what I see. I could be missing it but just want

Re: [AIP-34] Rewrite SubDagOperator

2020-08-05 Thread Jacob Ferriero
I really like this idea of a TaskGroup container as I think this will be much easier to use than SubDag. I'd like to propose an optional behavior for special retry mechanics via a TaskGroup.retry_all property. This way I could use TaskGroup to replace my favorite use of SubDag for atomically retry

Re: [DISCUSS] Moving stuff from CWiki to Github ?

2020-08-05 Thread Jarek Potiuk
I cleaned-up the CWiki : https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Home. It looks much better now. - Airflow 2.0 - Planning - Airflow Approach For Releases - Airflow Improvements Proposals - Announcements - File lists - To be moved The "outdated" pages are all

Re: [DISCUSS] Moving stuff from CWiki to Github ?

2020-08-05 Thread Kamil Breguła
+1 Perfect! On Wed, Aug 5, 2020 at 6:15 PM Jarek Potiuk wrote: > What do you think ? https://github.com/apache/airflow/issues/10176 (I > pinned it) > > On Wed, Aug 5, 2020 at 2:10 PM Jarek Potiuk > wrote: > > > I love the idea with Pinned Issue keeping "current initiatives". > > > > TL;DR; Summ

Re: [DISCUSS] Moving stuff from CWiki to Github ?

2020-08-05 Thread Jarek Potiuk
What do you think ? https://github.com/apache/airflow/issues/10176 (I pinned it) On Wed, Aug 5, 2020 at 2:10 PM Jarek Potiuk wrote: > I love the idea with Pinned Issue keeping "current initiatives". > > TL;DR; Summarizing the current proposal > > * We keep pretty much everything in labelled Gith

Re: Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls

2020-08-05 Thread Jarek Potiuk
+1 On Wed, Aug 5, 2020 at 1:55 PM Kaxil Naik wrote: > I have scheduled the first meeting (*Monday, 10 August* at *5:30 GMT*) on > the Shared Calendar. > > *Calendar Link*: > > https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t > The

Re: [DISCUSS] Moving stuff from CWiki to Github ?

2020-08-05 Thread Jarek Potiuk
I love the idea with Pinned Issue keeping "current initiatives". TL;DR; Summarizing the current proposal * We keep pretty much everything in labelled Github Issues (including "meta" issues) * We disable back Wiki in Github * We have a pinned issue with "Current Initiatives" linked * We cleanup CW

Re: Airflow 2.0 - Planning / Scoping / Tracking / Dev Calls

2020-08-05 Thread Kaxil Naik
I have scheduled the first meeting (*Monday, 10 August* at *5:30 GMT*) on the Shared Calendar. *Calendar Link*: https://calendar.google.com/calendar?cid=Y19kaGRoM2JkamM0MmM0bmd0bnBnN292Y3M5Z0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t The Calendar is also embedded on https://cwiki.apache.org/confluence/dis

Re: [DISCUSS] Moving stuff from CWiki to Github ?

2020-08-05 Thread Kamil Breguła
1. I do not see a problem. Issues may have a prefix in the title, which will allow us to easily find them. Release - Airflow 2.0 Release - Airflow 1.10 AIP-32 - API AIP-XXX - Docker Image/Helm Chart AIP-XXX - However, I do not mind using labels in this case. https://github.com/apache/airflo