Re: [DISCUSS] - LLM-Powered DAG Generation

Also you might take a look at Airflow Summit videos https://www.youtube.com/playlist?list=PLGudixcDaxY2NIjMYT8t5zA9KJ47wTCkM -> and look back to 2023. There were at least several talks about using LLMs to generate Airflow Dags, and our users are doing it already - and I guess it's quite natural for

Re: [DISCUSS] - LLM-Powered DAG Generation

FYI I added your email directly - because apparently you are not subscribed to devlist - please do subscribe following the "community" tab on our website. I don't want to cut down your wings and excitement, but this is a deliberate choice that Airflow UI does not allow to author DAGs. This is a se

[DISCUSS] - LLM-Powered DAG Generation

Hello Team, My name is Harikrishnan(Hari), I have an idea/improvement proposal for Airflow. LLM-powered feature within Apache Airflow to significantly enhance the DAG authoring experience. Users would be able to provide natural language descriptions or queries and leverage Large Language Models (

Re: [VOTE] Release Airflow 3.0.3 from 3.0.3rc3 & Task SDK 1.0.3 from 1.0.3rc3

+1 non-binding. Tested my migration fixes and ran a few dags. Best, Wei > On Jul 7, 2025, at 4:37 AM, Pavankumar Gopidesu > wrote: > > +1 non-binding. > > Tested a few examples: dags, LGTM. > > There is one default example dag broken with import errors, I have added a > fix here, https://gi

[Meeting Notes] Airflow 3 dev call - 3 July 2025

Hey everyone, Thank you to everyone who made the dev call last week. I updated our meeting notes document in the Airflow wiki to capture the notes. The link for those notes is here

Re: [VOTE] Release Airflow 3.0.3 from 3.0.3rc3 & Task SDK 1.0.3 from 1.0.3rc3

+1 non-binding. Tested a few examples: dags, LGTM. There is one default example dag broken with import errors, I have added a fix here, https://github.com/apache/airflow/pull/52956. Pavan On Sat, Jul 5, 2025 at 11:09 PM Jarek Potiuk wrote: > I think yes - if it appeared in 3.0.3 and was not

Re: Discuss: new option [secrets]backend_order

I think the only real "behavioural" change that you might expect from the user if they "know" what is the sequence is at the connection / variable UI. This is where the user (with connection/variable editing capabilities or connection/variable viewing capabilities) might actually make a different d

Re: Discuss: new option [secrets]backend_order

> This seems like organisation-wide policy that simply all DAG authors in the organization should be made aware of One among several other things that the admin expects users to remember. We should reduce it, not increase it. >From my point of view this setting adds a blind spot. I am not happy wi

Re: Discuss: new option [secrets]backend_order

> I am missing the part of how can DAG Author be aware of the backend order the cluster admin chooses? > This is a crucial part I am not sure there is a special need for it. This seems like organisation-wide policy that simply all DAG authors in the organization should be made aware of - it has 0

Re: Discuss: new option [secrets]backend_order

I am missing the part of how can DAG Author be aware of the backend order the cluster admin chooses? This is a crucial part. On Thu, Jul 3, 2025 at 12:14 PM Jarek Potiuk wrote: > Sorry for typos - that was my mobile auto complete... I hope it is > understandable anyway > > czw., 3 lip 2025, 11:1

Re: [DISCUSS] Consistent test assertion style: pytest-native vs unittest-style

Thank you @Potiuk for pointing out the intent behind the “one assert per test” principle, and @ash for highlighting how using dedicated mock assert functions can make the code easier to read and understand. These were perspectives I hadn’t fully considered, and I really appreciate you sharing them.

[ANNOUNCE] Apache Airflow Providers prepared on July 03, 2025 are released

Dear Airflow community, I'm happy to announce that new versions of Airflow Providers packages prepared on July 03, 2025 were just released. Full list of PyPI packages released is added at the end of the message. The source release, as well as the binary releases, are available here: https://airf

[RESULT][VOTE] Airflow Providers - release of July 03, 2025

Hello, Apache Airflow Providers prepared on July 03, 2025 have been accepted. edge3 and amazon providers are excluded and will have rc2. 4 "+1" binding votes received: - Elad Kalif - Jens Scheffler - Jarek Potiuk - Amogh Desai 1 "+1" non-binding votes received: - Pavankumar Gopidesu Vote thre

Re: [VOTE] Airflow Providers prepared on July 03, 2025

edge3 and amazon providers are excluded from this vote due to bugs found. On Sat, Jul 5, 2025 at 11:31 PM Jens Scheffler wrote: > @Elad just qualified that the bug I reported in > https://github.com/apache/airflow/issues/52922 is casued by PR #52000 in > Edge3 > > Therefore I'd propose to exclud