+1

Op ma 16 mrt. 2020 om 12:53 schreef Bas Harenslak
<[email protected]>:

> +1
>
> > On 16 Mar 2020, at 12:27, Ash Berlin-Taylor <[email protected]> wrote:
> >
> > +1 binding
> >
> > On Mar 16 2020, at 11:20 am, Kaxil Naik <[email protected]> wrote:
> >
> >> +1 (binding)
> >>
> >> On Mon, Mar 16, 2020 at 11:19 AM Jarek Potiuk <[email protected]
> >
> >> wrote:
> >>
> >>> Clarify: +1 (binding)
> >>>
> >>> On Mon, Mar 16, 2020 at 12:19 PM Jarek Potiuk <
> [email protected]>
> >>> wrote:
> >>>
> >>>> +1
> >>>>
> >>>> On Mon, Mar 16, 2020 at 12:16 PM Kaxil Naik <[email protected]>
> wrote:
> >>>>
> >>>>> Hey all,
> >>>>>
> >>>>> This email calls for a vote on the scope described in
> >>>>>
> >>>
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-33+Secrets+backend
> >>>>> and
> >>>>> the PR: https://github.com/apache/airflow/pull/6376
> >>>>>
> >>>>> *Note*: The PR is already merged but if this vote does not pass we
> will
> >>>>> revert it.
> >>>>>
> >>>>> Documentation on the pluggable secrets backend:
> >>>>>
> >>>>>
> >>>
> https://airflow.readthedocs.io/en/latest/howto/connection/index.html#alternative-secrets-backend
> >>>>>
> >>>>> *Details*
> >>>>>
> >>>>>   - This PR is backwards-compatible
> >>>>>   - Provides a pluggable mechanism where a developer can use
> >>> their own
> >>>>>   backend
> >>>>>   - When looking up a connection, by default airflow will search the
> >>>>>   Secrets Backend, followed by environment variables first and
> Metadata
> >>>>> DB.
> >>>>>   - Support for AWS SSM as Secret backend
> >>>>>
> >>>>>
> >>>>> Regards,
> >>>>> Kaxil
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Jarek Potiuk
> >>>> Polidea <https://www.polidea.com/> | Principal Software Engineer
> >>>>
> >>>> M: +48 660 796 129 <+48660796129>
> >>>> [image: Polidea] <https://www.polidea.com/>
> >>>>
> >>>>
> >>>
> >>> --
> >>>
> >>> Jarek Potiuk
> >>> Polidea <https://www.polidea.com/> | Principal Software Engineer
> >>>
> >>> M: +48 660 796 129 <+48660796129>
> >>> [image: Polidea] <https://www.polidea.com/>
> >>>
> >>
>
>

Reply via email to