Hi Vincent,
This looks promising!
We're using Keycloak, integrated with Airflow using the FAB auth manager
(OpenID). As of now, it has worked properly for us to login to the webpage,
but I never managed to get the API working for Keycloak users (I had to
create users using FAB directly).
We have
+1 for the opt-in feature. Can clearly see the need for this to exist. And
for both UI and APIs. +1 with Julian's idea of Dags waiting for input.
Thanks,
- Avi
On Wed, May 21, 2025 at 3:42 AM Kalyan Reddy wrote:
> I'm +1 on the idea. There should probably be notifications when approval
> is nee
I'm +1 on the idea. There should probably be notifications when approval is
needed to continue a task. Additionally, a dashboard would be helpful for
viewing the tasks awaiting my approval. It kind of makes me remember approval
gates on Azure DevOps pipelines. Even integrations to Slack/PagerDu
I like this idea. As Jens mentioned, this should be an opt-in feature, and
starting with providers seems reasonable. After that, we could probably get
feedback from users and see how we could improve UI/UX.
Best,
Wei
> On May 21, 2025, at 5:36 AM, Jens Scheffler
> wrote:
>
> Hi All,
>
> oh
Hi All,
oh I am a bit "envy" on receiving the email because I am thinking about
EXACTLY the same propsal but did not file an AIP to discuss about
this... as a matter of personal capacity and I wanted to finish off
existing obligations before dropping new ideas.
The very same idea for me was
Great news!
On Tue, 20 May 2025, 23:15 Jens Scheffler,
wrote:
> Very cool! Hope this helps uns as an increment to get to 3.0 soon!
>
> On 20.05.25 12:57, Amogh Desai wrote:
> >
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Tue, May 20, 2025 at 2:40 PM Kaxil Naik wrote:
> >
> >>
Very cool! Hope this helps uns as an increment to get to 3.0 soon!
On 20.05.25 12:57, Amogh Desai wrote:
Thanks & Regards,
Amogh Desai
On Tue, May 20, 2025 at 2:40 PM Kaxil Naik wrote:
Dear Airflow community,
I'm happy to announce that Airflow 2.11.0 was just released.
The released
+1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
Licenses, Signatures
On 20.05.25 12:57, Amogh Desai wrote:
+1 non binding.
Checked the changes, they look fine.
Thanks & Regards,
Amogh Desai
On Tue, May 20, 2025 at 3:47 PM Kaxil Naik wrote:
+1 binding : checked si
Oh, this could be cool! But quite specific since not everyone has Keycloak
for auth things and Airflow still has to have some own one.
May be not full delegation, but some sort of synchronization could be a
great middle ground. Airflow works like it always been, while source of
auth info becomes Ke
I like the idea! We built something similar where a task would send an
email with a report attached (Excel, of course). The user had to either
approve the report or flag an issue. If they didn't respond in 2 hours, it
escalated to a backup, then to the department lead. If no one responded,
the DAG
While this is an understandable idea, I think it's wrong to involve humans
to take a part into Airflow workflow.
Run with parameters. Read the logs. Retry.
Blocking the whole pipeline could not be acceptable: humans are not stable
resource for input, they may be sick or on vacation and who will be
I like this idea. Three notes/comments that come to mind:
I think API interactions are going to be critical here. For example, I could
imagine someone wanting to post a message to slack with a button to resume the
DAG without having to go back to the Airflow UI
I see this as being useful for a lo
I'm late to the party (I was out of office and offline for the last two
weeks) so I only saw this now!! Thank you so much!! Means a lot to me
On Sat, May 10, 2025 at 2:37 AM Amogh Desai
wrote:
> Superb!
>
> Happy to see Constance vs Constrance :)
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Sat,
Hey everyone,
This is a small technical change, but conceptually it is significant and
therefore bringing it to the devlist.
As we have been having conversations with Airflow users, who are using
Airflow for Gen AI applications, there are a couple of features that have
been brought up as being de
Hi everyone,
Here is a quick reminder that we have our Airflow 3 dev call the day after
tomorrow at Thursday, 22nd May 2025 at 8AM PST (11 am EST | 4 pm UTC /
GMT).
Proposed agenda:
1. Catch-up on action items from last call:
- Docs site update (Elad, Jarek)
- Example Dags update (Jens, Jarek)
2
Thanks Jarek, for your thoughts, yes opendalfs was one of the packages
available but not that maintained well and it has
less integrations between opendal file systems. Right now, it supports only
S3, fs, and in-memory file systems.
I agree that it may be more suitable for a TaskFlow-based approach
Good point.
You're right — it's already possible to use Keycloak for user authentication
with the FAB (Flask AppBuilder) auth manager. You can configure FAB to use
Keycloak as an identity provider, allowing users to authenticate via Keycloak.
Authorization, however, remains handled within FAB,
Hi!
Sounds great, but Airflow already works perfectly to auth users via
Keycloak LDAP protocol. What this provider will change and why it will be
better than now?
--
,,,^..^,,,
On Tue, May 20, 2025 at 7:32 PM Beck, Vincent
wrote:
> Hi all,
>
> I'd like to propose adding a new provider, Keycloa
Hi all,
I'd like to propose adding a new provider, Keycloak [1], to the collection of
Apache Airflow providers.
Keycloak is an open-source software product to allow single sign-on with
identity and access management aimed at modern applications and services.
The intent of this new provider wou
Hey fellow Airflowers,
I have cut the first release candidate for the Apache Airflow Python Client
3.0.0.
This email is calling for a vote on the release,
which will last for 72 hours. Consider this my (binding) +1.
Airflow Client 3.0.0rc2 is available at:
https://dist.apache.org/repos/dist/dev/a
Cancelling the vote due to the pydantic limit. I will cut rc2 next
On Tue, 20 May 2025 at 16:56, Kaxil Naik wrote:
> Yeah, agreed. I'll create rc2 fixing the urllib limit
>
> On Tue, 20 May 2025 at 07:19, Jarek Potiuk wrote:
>
>> +1 binding - but with a few caveats, and some bad consequences if
Yeah, agreed. I'll create rc2 fixing the urllib limit
On Tue, 20 May 2025 at 07:19, Jarek Potiuk wrote:
> +1 binding - but with a few caveats, and some bad consequences if we
> release it (up to Kaxil to decide)
>
> Tested reproducibility, checksums signatures, licences are ok since all the
> co
Thanks & Regards,
Amogh Desai
On Tue, May 20, 2025 at 2:40 PM Kaxil Naik wrote:
> Dear Airflow community,
>
> I'm happy to announce that Airflow 2.11.0 was just released.
>
> The released sources and packages can be downloaded via
>
> https://airflow.apache.org/docs/apache-airflow/2.11.0/
+1 non binding.
Checked the changes, they look fine.
Thanks & Regards,
Amogh Desai
On Tue, May 20, 2025 at 3:47 PM Kaxil Naik wrote:
> +1 binding : checked signature & license
>
> On Tue, 20 May 2025 at 15:27, Elad Kalif wrote:
>
> > Hey all,
> >
> > I have just cut the new wave Airflow Prov
+1 binding : checked signature & license
On Tue, 20 May 2025 at 15:27, Elad Kalif wrote:
> Hey all,
>
> I have just cut the new wave Airflow Providers packages. This email is
> calling a vote on the release, which will last for *24 hours* - which means
> that it will end on May 21, 2025 09:55 AM
Hey all,
I have just cut the new wave Airflow Providers packages. This email is
calling a vote on the release, which will last for *24 hours* - which means
that it will end on May 21, 2025 09:55 AM UTC and until 3 binding +1 votes
have been received. This is a shortened (24 hours vote) as agreed b
Dear Airflow community,
I'm happy to announce that Airflow 2.11.0 was just released.
The released sources and packages can be downloaded via
https://airflow.apache.org/docs/apache-airflow/2.11.0/installation/installing-from-sources.html
Other installation methods are described in
https://airflow
Hello Airflow Community,
The vote to release Apache Airflow version 2.11.0 based on 2.11.0rc1 is now
closed.
The vote PASSED with 4 binding "+1", 7 non-binding "+1" and 0 "-1" votes:
*"+1" Binding votes*:
- Kaxil Naik
- Jens Scheffler
- Jed Cunningham
- Ephraim Anierobi
*"+1" non-Binding votes
+1 (binding) Checked licenses, signatures, checksums and reproducibility.
On Tue, 20 May 2025 at 08:12, kalyan reddy wrote:
> +1 (non-binding)
>
> From: Jed Cunningham
> Sent: 20 May 2025 12:13
> To: dev@airflow.apache.org
> Subject: Re: [VOTE] Release Airflow
+1 (non-binding)
From: Jed Cunningham
Sent: 20 May 2025 12:13
To: dev@airflow.apache.org
Subject: Re: [VOTE] Release Airflow 2.11.0 from 2.11.0rc1
+1 (binding) Checked reproducibility, signatures, checksums, licences. Used
it with the helm chart with a few differ
+1 (non-binding)
On Tue, 20 May 2025, 08:43 Jed Cunningham, wrote:
> +1 (binding) Checked reproducibility, signatures, checksums, licences. Used
> it with the helm chart with a few different configs.
>
31 matches
Mail list logo
