Re: Jira cleanup and triage

On Wed, Aug 22, 2018 at 6:51 PM Driesprong, Fokko wrote: > Recently we've moved the Apache Airflow repo to the Gitbox repo ( > https://gitbox.apache.org/). Before with the Apache repo, the Github repo > was just a mirror of the Apache one. Now we do everything on Github itself. > We still need

Re: Airflow & AWS Lambda Tutorials?

Hey Andrew - My suggestions are similar to Marcel's. I favor invoking the Lambda function with the invoke call in boto3 in a PythonOperator, or using the AwsHook if that abstraction adds value here vs

Re: PR Review Dashboard?

I mean a few ASF projects update JIRA tickets based on PRs automatically. Switching from JIRA to GH issues (or back) is super painful, so I’d probably do more incremental improvements personally, I just don’t have the time to do something like that. I’ll take a look at some the K8s tools (over in

Separate logging level

Hi, We use Airflow and encountered a significant volume of logs. Is it possible to separately determine the level of logging for Airflow and Dags, for example "error" for Airflow, to reduce the amount of logs in the folder "/logs/scheduler", and "info" for Dags, to have all the information

Re: PR Review Dashboard?

Kubernetes is a good place to look as they've invested a lot in github bots and label based workflows. E.g. the cherry-picking script and doc is here: https://github.com/kubernetes/kubernetes/blob/master/hack/cherry_pick_pull.sh