+1 binding, will be happy to help in the implementation :)

Shahar

On Mon, Jul 7, 2025 at 9:27 PM Jarek Potiuk <ja...@potiuk.com> wrote:

> Hello Airflow community,
>
> I would like to call a vote on "reloaded" version of the AIP
>
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-team+deployment+of+Airflow+components
>
> The last discussion thread about "reloading" of the AIP is here
> https://lists.apache.org/thread/oqj804phspmrj7d798899pz237f3w6c2
> Previous discussion here:
> https://lists.apache.org/thread/6k3sxxvboko4fw7qdhr78y3qhf26vh3q previous
> voting thread:
> https://lists.apache.org/thread/kvc0stsbm25fngmld3npv2xcpxz3o2kt, previous
> vote result thread:
> https://lists.apache.org/thread/t3q5tlp5drmr0f9c6mxglggfljtyxoct
>
> Based on the last discussions, the original proposal has been significantly
> trimmed down and simplified with the main focus on minimising the impact on
> Airflow code base and with the following goals:
>
> * less operational overhead for managing multi-team (once AIP-72 is
> complete) where separate execution environments are important
> * virtual assets sharing between teams
> * ability of having "admin" and "team sharing" capability where dags from
> multiple teams can be seen in a single Airflow UI (requires custom RBAC an
> AIP-56 implementation of Auth Manager - with KeyCloak Auth Manager being a
> reference implementation)
>
> The vote will run for ~7 days and last till next Monday, the 14th of July
> 2025 18:30 UTC.
>
> Countdown timer:
>
> https://www.timeanddate.com/countdown/generic?iso=20250714T1830&p0=1440&font=cursive
>
> Everyone is encouraged to vote, although only PMC members and Committer's
> votes are considered binding.
>
> Consider this +1 (binding) from me.
>
> J.
>

Reply via email to