e. It's important to focus on building what users are
> asking for.
>
>
> From: Shahar Epstein
> Sent: Wednesday, August 7, 2024 10:58:27 AM
> To: dev@airflow.apache.org
> Subject: RE: [EXT] [VOTE] AIP-67 - Multi-team deplyment of Airflow
&
tant to focus on building what users are
> asking for.
>
>
> From: Shahar Epstein
> Sent: Wednesday, August 7, 2024 10:58:27 AM
> To: dev@airflow.apache.org
> Subject: RE: [EXT] [VOTE] AIP-67 - Multi-team deplyment of Airflow
> Components
>
om: Shahar Epstein
Sent: Wednesday, August 7, 2024 10:58:27 AM
To: dev@airflow.apache.org
Subject: RE: [EXT] [VOTE] AIP-67 - Multi-team deplyment of Airflow Components
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the
+1 (binding)
Looking forward!
On 2024/08/01 20:13:00 Jarek Potiuk wrote:
> Hello here,
>
> I reviewed and - I hope - addressed all the comments so far. One most
> recent change in the doc was to allow a connection/variable to belong to
> multiple teams. Also I mentioned a potential future change
; > dependencies, as you mentioned in the email.
> > > >
> > > >
> > > >
> > > >
> > > > Looking forward.
> > > >
> > > >
> > > >
> > > >
> > > > Regards,
> > > > Kaxil
> &
nding.
> > > >
> > > > Many thougths and discussions went into this AIP. Also User survery
> > showed
> > > > a strong demand for this - same we have also in our house. A multi
> team
> > > > setup is eagerly needed.
> > > > Nevert
gt; > setup is eagerly needed.
> > > Nevertheless the complexity and missing turn-key delivery will be a
> > > challenge. I assume it needs to evolve.
> > > Besides a bit sceptic words the possibilities rule-out the additional
> > > complexity. I think
- especially not with
> > options to have some more breaking changes in AF3 is the right point to
> > plan all meede structural changes in! Thanks Jarek for driving this!
> >
> > Sent from Outlook for iOS<https://aka.ms/o0ukef>
> > <https://aka.ms/o0ukef>
t;mailto:ja...@potiuk.com>>>
> Sent: Thursday, August 1, 2024 10:40:16 PM
> To: dev@airflow.apache.org <mailto:dev@airflow.apache.org>
> <mailto:dev@airflow.apache.org <mailto:dev@airflow.apache.org>>
> mailto:dev@airflow.apache.org>
> <mailto:dev@airflo
che.org <mailto:dev@airflow.apache.org>
> mailto:dev@airflow.apache.org>>
> Subject: Re: [VOTE] AIP-67 - Multi-team deplyment of Airflow Components
>
> Voting ends a week from now - i.e Thursday 8th of August 2023 (midnight).
>
> On Thu, Aug 1, 2024 at 10:13 PM Jarek Poti
anks Jarek for driving this!
>
> Sent from Outlook for iOS<https://aka.ms/o0ukef>
>
> From: Jarek Potiuk
> Sent: Thursday, August 1, 2024 10:40:16 PM
> To: dev@airflow.apache.org
> Subject: Re: [VOTE] AIP-67 - Multi-team deplyment of Airfl
for iOS<https://aka.ms/o0ukef>
From: Jarek Potiuk
Sent: Thursday, August 1, 2024 10:40:16 PM
To: dev@airflow.apache.org
Subject: Re: [VOTE] AIP-67 - Multi-team deplyment of Airflow Components
Voting ends a week from now - i.e Thursday 8th of August 2023 (mi
+1 non-binding
I’m looking forward to seeing this AIP as it will pave the way for
follow-up features that enable fully manageable multi-tenancy. I’m also
excited about the opportunity to work on this. 🙌
On Thu, Aug 1, 2024 at 10:40 PM Jarek Potiuk wrote:
> Voting ends a week from now - i.e Thurs
Voting ends a week from now - i.e Thursday 8th of August 2023 (midnight).
On Thu, Aug 1, 2024 at 10:13 PM Jarek Potiuk wrote:
> Hello here,
>
> I reviewed and - I hope - addressed all the comments so far. One most
> recent change in the doc was to allow a connection/variable to belong to
> multi
Hello here,
I reviewed and - I hope - addressed all the comments so far. One most
recent change in the doc was to allow a connection/variable to belong to
multiple teams. Also I mentioned a potential future change that will allow
us to run "per-team" schedulers - leaving the UI/DB schema as the ma
15 matches
Mail list logo
