Rafael,
I think the key component here is your CI/CD pipeline and PR standards. I limit
who can approve PRs, who can approve a release (not always the same people),
and require vulnerability scanning on all containers and the DAGs within those
containers before a PR and release to prod are appr
+1
> On Jun 11, 2019, at 8:23 AM, Jarek Potiuk wrote:
>
> +1 (binding)
>
> On Tue, Jun 11, 2019 at 1:43 PM Jiajie Zhong
> wrote:
>
>> +1 (non-binding)
>>
>>
>> Best Wish
>> — Jiajie
>>
>>
>>
>> On Jun 11, 2019, at 19:21, Kaxil Naik > kaxiln...@gmail.com>> wrote:
>>
>> +1 (binding)
>>
>
Great questions. This makes two of us thinking about data lineage inside and/or
outside of airflow.
Thank you for the questions Germain.
Cheers,
Jason
> On Jun 6, 2019, at 9:19 AM, Germain TANGUY
> wrote:
>
> Hello everyone,
> We were wondering if some of you are using a data lineage solut
+1
Quick question, could we also push user@ threads to a specified Slack channel?
Cheers,
Jason
> On May 24, 2019, at 8:23 AM, Teresa Martyny
> wrote:
>
> Jared makes a good point about Slack. It seems like the Slack group
> channels are mostly troubleshooting questions in spite of their nam