+1 binding Best, Wei
> On Apr 17, 2026, at 2:56 PM, Amogh Desai <[email protected]> wrote: > > +1 binding. > > Thanks & Regards, > Amogh Desai > > > On Fri, Apr 17, 2026 at 2:34 AM Kaxil Naik <[email protected]> wrote: > >> +1 binding >> >> On Thu, 16 Apr 2026 at 19:03, Shrividya Hegde <[email protected] >>> >> wrote: >> >>> +1 from me >>> >>> On Thu, Apr 16, 2026 at 1:42 PM Buğra Öztürk <[email protected]> >>> wrote: >>> >>>> +1 (binding) >>>> >>>> On Thu, Apr 16, 2026 at 5:08 PM Piyush Mudgal < >>> [email protected] >>>>> >>>> wrote: >>>> >>>>> +1 from me >>>>> >>>>> On Thu, Apr 16, 2026 at 1:39 AM Jens Scheffler <[email protected]> >>>>> wrote: >>>>> >>>>>> +1 (binding) >>>>>> >>>>>> On 15.04.26 15:28, Jarek Potiuk wrote: >>>>>>> Aha .. Thanks Elad. +1 (binding) then. >>>>>>> >>>>>>> On Wed, Apr 15, 2026 at 10:30 AM Elad Kalif <[email protected]> >>>>> wrote: >>>>>>> >>>>>>>> Jarek, the current protocol allows lazy consensus only for open >>>> source >>>>>>>> based providers. Regardless, in the upcoming days I will raise a >>>>>> proposal >>>>>>>> to simplify the process thus a vote won't be needed at all. >>>>>>>> >>>>>>>> As for the vote: +1 binding >>>>>>>> >>>>>>>> בתאריך יום ד׳, 15 באפר׳ 2026, 11:00, מאת Jarek Potiuk < >>>>>> [email protected]>: >>>>>>>> >>>>>>>>> Suggestion -> you should likely call for LAZY CONSENSUS: this >>>> seems >>>>>>>>> non-controversial and consensus will pass when the time passes >>> and >>>>>> no-one >>>>>>>>> objects. >>>>>>>>> >>>>>>>>> On Wed, Apr 15, 2026 at 8:28 AM Barak Abekasis < >>>> [email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Airflow community, >>>>>>>>>> >>>>>>>>>> Following the [DISCUSSION] thread [1], I'd like to call a vote >>> on >>>>>>>>> accepting >>>>>>>>>> the **Akeyless Vault Platform** provider into the Apache >> Airflow >>>>>>>> monorepo >>>>>>>>>> as an incubating community provider, per the process in >>>>>>>>>> ACCEPTING_PROVIDERS.rst [2]. >>>>>>>>>> >>>>>>>>>> ## Provider overview >>>>>>>>>> >>>>>>>>>> Akeyless (https://www.akeyless.io/) is a SaaS-based secrets >>>>>> management >>>>>>>>> and >>>>>>>>>> zero-trust access platform. The provider adds native Airflow >>>>>>>> integration >>>>>>>>>> for >>>>>>>>>> managing secrets across DAG workflows. >>>>>>>>>> >>>>>>>>>> **Components:** >>>>>>>>>> >>>>>>>>>> | Component | Class | >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>> >>>>> >>>> >>> >> |--------------------|-------------------------------------------------------------| >>>>>>>>>> | Hook | >>> `airflow.providers.akeyless.hooks.akeyless.AkeylessHook` >>>> | >>>>>>>>>> | Connection type | `akeyless` (custom UI fields for 8 auth >>>>> methods) | >>>>>>>>>> | Secrets Backend | >>>>>>>>>> `airflow.providers.akeyless.secrets.akeyless.AkeylessBackend` >> | >>>>>>>>>> >>>>>>>>>> **Authentication methods:** API Key, AWS IAM, GCP, Azure AD, >>>>> Universal >>>>>>>>>> Identity (UID), JWT/OIDC, Kubernetes, Certificate >>>>>>>>>> >>>>>>>>>> **Dependencies:** `akeyless>=5.0.0` (Apache 2.0 licensed, >> ~350K >>>>>> monthly >>>>>>>>>> PyPI downloads). Optional: `akeyless_cloud_id` for cloud-based >>>> auth. >>>>>>>>>> >>>>>>>>>> The hook is a thin wrapper over the official `akeyless` Python >>>> SDK. >>>>>> The >>>>>>>>>> secrets backend follows the same pattern as the HashiCorp >> Vault >>>>>>>> backend. >>>>>>>>>> ## Pull request >>>>>>>>>> >>>>>>>>>> https://github.com/apache/airflow/pull/64754 >>>>>>>>>> >>>>>>>>>> The PR includes: >>>>>>>>>> - Full RST documentation (connection guide, secrets backend >>> guide) >>>>>>>>>> - Unit tests for hook (11 tests) and secrets backend (8 tests) >>>>>>>>>> - Example system test DAG >>>>>>>>>> - `provider.yaml` with connection field schema >>>>>>>>>> - All provider CI checks passing (Non-DB, DB, Compat, MyPy, >> docs >>>>>> build) >>>>>>>>>> >>>>>>>>>> ## Stewards and sponsoring committer >>>>>>>>>> >>>>>>>>>> - **Barak Abekasis** (@baraka-akeyless) — Akeyless >> integrations >>>> team >>>>>>>>>> (steward) >>>>>>>>>> - **Dean Sher** (@deanshak) — [Product Architect] (co-steward) >>>>>>>>>> - **Sponsoring committer:** [Elad Kal] (@eladkal) >>>>>>>>>> >>>>>>>>>> ## Incubation commitment >>>>>>>>>> >>>>>>>>>> We commit to meeting incubation health metrics within 6 >> months: >>>>>>>>>> - Timely PR reviews (< 7 days) >>>>>>>>>> - Issue triage and resolution >>>>>>>>>> - Keeping dependencies up to date >>>>>>>>>> - Participating in quarterly governance updates >>>>>>>>>> >>>>>>>>>> ## Vote >>>>>>>>>> >>>>>>>>>> Please vote: >>>>>>>>>> >>>>>>>>>> [ ] +1 Accept apache-airflow-providers-akeyless as an >> incubating >>>>>>>> provider >>>>>>>>>> [ ] +0 No opinion >>>>>>>>>> [ ] -1 Do not accept (please provide reason) >>>>>>>>>> >>>>>>>>>> The vote follows the Apache Software Foundation rules for >> Votes >>> on >>>>>> Code >>>>>>>>>> Modification [3]. The vote will be open for at least 72 hours. >>>>>>>>>> >>>>>>>>>> [1] [DISCUSSION] thread link: >>>>>>>>>> >>>>> https://lists.apache.org/[email protected]:lte=1M:akeyless >>>>>>>>>> [2] >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>> >>>>> >>>> >>> >> https://github.com/apache/airflow/blob/main/providers/ACCEPTING_PROVIDERS.rst >>>>>>>>>> [3] >>>>>>>>>> >>>>>>>> >>>>>> >>>> >> https://www.apache.org/foundation/voting.html#votes-on-code-modification >>>>>>>>>> [image: Kind regards,] >>>>>>>>>> >>>>>>>>>> [image: photo] >>>>>>>>>> >>>>>>>>>> Barak Abekasis >>>>>>>>>> Solution Architect, Akeyless >>>>>>>>>> >>>>>>>>>> [image: icon] +972-526238465 [image: icon] >> [email protected] >>>>>>>> [image: >>>>>>>>>> icon] akeyless.io >>>>>>>>>> >>>>>>>>>> [image: youtube] <https://www.youtube.com/@Akeyless> >>>>>>>>>> >>>>>>>>>> [image: facebook] <https://www.facebook.com/Akeylessio> >>>>>>>>>> >>>>>>>>>> [image: linkedin] <https://www.linkedin.com/company/akeyless/ >>> >>>>>>>>>> >>>>>>>>>> [image: twitter] <https://x.com/akeylessio> >>>>>>>>>> >>>>>>>>>> [image: Meeting Button App] < >>>>>>>> https://meetings.hubspot.com/barak-abekasis >>>>>>>>>> >>>>>>>>>> [image: App Banner Image] <https://hubs.li/Q04bfrFp0> >>>>>>>>>> >>>>>>>>>> [image: __tpx__] >>>>>>>>>> >>>>>> >>>>>> >> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>> >>>> >>> >>
