Thanks Jarek for the rework. I see added complexity for Multi-Team but
given the current state of 3.0 I think it is well thought to strip-off
complexity. Much better than the original AIP. I like the current
approach much more like the previous.
+1 binding.
Nit: Multi-Team Pluing support might be "nice", I'd put this at the end
of priority of all implementations you described. Maybe even optional.
On 08.07.25 14:22, Jarek Potiuk wrote:
This vote is to update AIP-67 with clarifications. The old AIP is still
properly voted in. If we want to "unvote" AIP-67 in it's entirety - that
would be another - different vote I guess.
On Tue, Jul 8, 2025 at 2:13 PM Ash Berlin-Taylor <a...@apache.org> wrote:
Can I ask for clarification on what we are voting on here: Is it “the new
AIP-67 proposal vs the old one” or “the new AIP-67 vs nothing”?
On 7 Jul 2025, at 19:26, 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
