Re: [DISCUSS] confusing alert re SimpleAuthManager

[Daniel Standish]

I should add, the import here is, many users who never customized auth
before will now see this message and not really have a clue what they are
supposed to do, and I think it will probably create a good amount of
confusion.

On Thu, Mar 20, 2025 at 10:27 AM Daniel Standish <
daniel.stand...@astronomer.io> wrote:

> I just saw this when spinning up airflow
>
> [image: image.png]
>
> I think the message is confusing / misleading / not very helpful.
>
> There's nothing necessarily wrong with having simple auth or no auth if
> you control access some other way.  Moreover we don't tell users what they
> should do instead!
>
> So I think we should either remove this bubble or add more nuance and
> point them in a direction that will lead them to what we *do* recommend.
>
>

Re: New committer: Rahul Vats

[Shubham Raj]

Congrats Rahul, well deserved!!

On Tue, 1 Apr 2025 at 00:33, Vishnu Chilukoori 
wrote:

> Congrats Rahul...well deserved!!
>
>
> --
> Regards,
> Vishnu Chilukoori
>
> On Mon, Mar 31, 2025 at 11:53 AM Idris Adebisi
>  wrote:
>
> >  Congratulations, Rahul!
> >
> > On Monday, March 31, 2025 at 07:45:27 PM GMT+1, Ambika Garg <
> > ambikagarg1...@gmail.com> wrote:
> >
> >  Congratulations Rahul!!
> > On Mon, Mar 31, 2025 at 2:43 PM Ankit Chaurasia 
> > wrote:
> >
> > > Congratulations, Rahul! Well deserved.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Apr 1, 2025 at 12:16 AM Constance Martineau
> > >  wrote:
> > >
> > > > Congrats Rahul! Well deserved :)
> > > >
> > > > On Mon, Mar 31, 2025 at 2:28 PM Oliveira, Niko
> > >  > > > >
> > > > wrote:
> > > >
> > > > > Congrats Rahul, great work!
> > > > >
> > > > > 
> > > > > From: Jed Cunningham 
> > > > > Sent: Monday, March 31, 2025 11:19:53 AM
> > > > > To: dev@airflow.apache.org
> > > > > Subject: [EXT] New committer: Rahul Vats
> > > > >
> > > > > CAUTION: This email originated from outside of the organization. Do
> > not
> > > > > click links or open attachments unless you can confirm the sender
> and
> > > > know
> > > > > the content is safe.
> > > > >
> > > > >
> > > > >
> > > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur
> > > externe.
> > > > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous
> ne
> > > > pouvez
> > > > > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas
> > certain
> > > > que
> > > > > le contenu ne présente aucun risque.
> > > > >
> > > > >
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Airflow
> > > > > has invited Rahul Vats to become a committer and we are pleased
> > > > > to announce that they have accepted.
> > > > >
> > > > > Please join us in welcoming Rahul to their new role and
> > > > > responsibility in our project community.
> > > > >
> > > > > Rahul has had a tremendous impact on Airflow 3, primarily around
> > > testing.
> > > > > Thanks Rahul, welcome, it's well deserved!
> > > > >
> > > > > Jed
> > > > > On behalf of the Apache Airflow PMC
> > > > >
> > > >
> > >
> >
>

Re: Airflow Mentors for Summer 2025 MLH Fellowship

[Jarek Potiuk]

Same here as Dennis and Amogh . This is good stuff :). But with Airflow 3/
Security work, hard for me to commit - but happy to help with code reviews
and such :)

On Sat, Apr 5, 2025 at 7:47 AM Amogh Desai  wrote:

> Hey Everyone,
>
> I also worked with Alex and his team during the fall of 2023 and it was an
> amazing experience.
>
> Mentoring some young college folks into a project foreign to them is very
> rewarding both for them as well as
> for the mentor. As a mentor, i learnt a lot during this process due to the
> beginner doubts and issues the mentees
> ran into which we often ignore as solving such issues seems trivial to us.
> This led to a lot of improvements
> in breeze as well during that time.
>
> Similar to Dennis, I won't be able to commit the time required (which isn't
> a lot btw) and I also want to give this
> chance to others as well :)
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Sat, Apr 5, 2025 at 2:32 AM Ferruzzi, Dennis
> 
> wrote:
>
> > Hey.  As Alex mentioned, I've worked with them for a couple of cohorts.
> > The only reason I'm not doing the next one is because I have a lot going
> on
> > in Real Life this summer and won't be able to commit the time.  If anyone
> > is interested but wants to chat about what it's like, feel free to hit me
> > up on the Slack channel.
> >
> >
> >  - ferruzzi
> >
> >
> > 
> > From: karan alang 
> > Sent: Thursday, April 3, 2025 4:38 PM
> > To: dev@airflow.apache.org; al...@majorleaguehacking.com
> > Subject: RE: [EXT] Airflow Mentors for Summer 2025 MLH Fellowship
> >
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you can confirm the sender and
> know
> > the content is safe.
> >
> >
> >
> > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe.
> > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne
> pouvez
> > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain
> que
> > le contenu ne présente aucun risque.
> >
> >
> >
> > Hi Alex,
> >
> > I'm happy to help out with this.
> >
> > regds,
> > Karan Alang
> >
> >
> > On Thu, Apr 3, 2025 at 4:13 PM Alex Gornet
> >  wrote:
> >
> > > Hi Airflow team,
> > >
> > > I'm Alex Gornet, a Partner Success Manager at Major League Hacking.
> Here
> > at
> > > MLH we run an Open Source Fellowship program
> > >  that functions like an internship
> > for
> > > student developers to contribute to open source projects. *Fellows from
> > our
> > > program have successfully contributed to Airflow since Fall 2024. *
> > >
> > > This year Royal Bank of Canada is sponsoring some seats in the program,
> > and
> > > they'd like their Fellows to contribute to Airflow as a way to give
> back
> > to
> > > the community. *With the recent release of Airflow 3.0, these Fellows
> > would
> > > be great candidates for tackling the backlog of bugs / issues following
> > the
> > > transition. *
> > >
> > > *Right now, we're looking for maintainers / core contributors to
> provide
> > > technical mentorship to the students*, so we'd love your help to
> > identify 2
> > > maintainers / core contributors (or more!) who could take lead here and
> > > support us bringing on some great new contributors.
> > >
> > >- *The program runs from May 19th to August 8th*, and we'd ask for
> ~2
> > >hours of your time each week.
> > >
> > > *If this is something you'd be interested in helping out with, you can
> > > simply reply to this email or reach out to me directly at
> > > al...@majorleaguehacking.com * — since
> > we're
> > > not too far out from program launch, the sooner you can let us know the
> > > better!
> > >
> > > If you have any questions about the program or want to chat more about
> > it,
> > > let me know and I'm happy to find time. You can also reach out to
> Dennis
> > > Ferruzzi who has mentored the last couple of cohorts to hear more about
> > his
> > > mentoring experience.
> > >
> > > Best,
> > > Alex
> > >
> >
>

Re: New committer: Rahul Vats

[Vishnu Chilukoori]

Congrats Rahul...well deserved!!


--
Regards,
Vishnu Chilukoori

On Mon, Mar 31, 2025 at 11:53 AM Idris Adebisi
 wrote:

>  Congratulations, Rahul!
>
> On Monday, March 31, 2025 at 07:45:27 PM GMT+1, Ambika Garg <
> ambikagarg1...@gmail.com> wrote:
>
>  Congratulations Rahul!!
> On Mon, Mar 31, 2025 at 2:43 PM Ankit Chaurasia 
> wrote:
>
> > Congratulations, Rahul! Well deserved.
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Apr 1, 2025 at 12:16 AM Constance Martineau
> >  wrote:
> >
> > > Congrats Rahul! Well deserved :)
> > >
> > > On Mon, Mar 31, 2025 at 2:28 PM Oliveira, Niko
> >  > > >
> > > wrote:
> > >
> > > > Congrats Rahul, great work!
> > > >
> > > > 
> > > > From: Jed Cunningham 
> > > > Sent: Monday, March 31, 2025 11:19:53 AM
> > > > To: dev@airflow.apache.org
> > > > Subject: [EXT] New committer: Rahul Vats
> > > >
> > > > CAUTION: This email originated from outside of the organization. Do
> not
> > > > click links or open attachments unless you can confirm the sender and
> > > know
> > > > the content is safe.
> > > >
> > > >
> > > >
> > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur
> > externe.
> > > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne
> > > pouvez
> > > > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas
> certain
> > > que
> > > > le contenu ne présente aucun risque.
> > > >
> > > >
> > > >
> > > > The Project Management Committee (PMC) for Apache Airflow
> > > > has invited Rahul Vats to become a committer and we are pleased
> > > > to announce that they have accepted.
> > > >
> > > > Please join us in welcoming Rahul to their new role and
> > > > responsibility in our project community.
> > > >
> > > > Rahul has had a tremendous impact on Airflow 3, primarily around
> > testing.
> > > > Thanks Rahul, welcome, it's well deserved!
> > > >
> > > > Jed
> > > > On behalf of the Apache Airflow PMC
> > > >
> > >
> >
>

Re: New committer: Rahul Vats

[Sumit Maheshwari]

Congratulations Rahul 🎉

On Wed, Apr 2, 2025 at 4:59 PM Freddy Demiane 
wrote:

> Congratulations Rahul!
>
> On Wed, Apr 2, 2025 at 12:27 PM Rahul Vats  wrote:
>
> > Thank you, everyone. It is great to be part of the team. I truly
> appreciate
> > all the guidance and support from the community.
> >
> > Regards,
> > Rahul Vats
> >
> > On Wed, 2 Apr 2025 at 13:43, Shahar Epstein  wrote:
> >
> > > Congratulation Rahul! :)
> > >
> > > On Mon, Mar 31, 2025, 21:20 Jed Cunningham 
> > > wrote:
> > >
> > > > The Project Management Committee (PMC) for Apache Airflow
> > > > has invited Rahul Vats to become a committer and we are pleased
> > > > to announce that they have accepted.
> > > >
> > > > Please join us in welcoming Rahul to their new role and
> > > > responsibility in our project community.
> > > >
> > > > Rahul has had a tremendous impact on Airflow 3, primarily around
> > testing.
> > > > Thanks Rahul, welcome, it's well deserved!
> > > >
> > > > Jed
> > > > On behalf of the Apache Airflow PMC
> > > >
> > >
> >
>

Re: [ANNOUNCEMENT] airflow-core is there (finally!)

[Vincent Beck]

It has never been simpler to contribute to Airflow! Awesome job Jarek :)

On 2025/03/21 13:50:05 Jarek Potiuk wrote:
> Quick additional info - if you have in your repo a 'tests` or 'airflow'
> folder remaining in the root of the repo - because you had some extra files
> in those (for example generated node_modules)  - you should delete those
> two directories. They are now unused and any files remaining there can and
> *SHOULD* be deleted
> 
> pt., 21 mar 2025, 14:28 użytkownik Jarek Potiuk  napisał:
> 
> > Ok. Now the "airflow-core" change is merged.
> >
> > Most important - *please rebase all your work now to the latest main*.
> > Most PR will have conflicts and will require to be rebased anyway, but you
> > will do you a favour if you do it manually first.
> >
> > Most likely those rebases will not work from the UI (they will just ask
> > you to do the rebase manual way and give some hints on how this can be done.
> >
> > If you have apache airflow repo set as remote, (I have 'apache' remote),
> > this can be usually done with:
> >
> > git fetch apache
> > git rebase --onto apache/main $(git merge-base)
> >
> > Of course you have to check it manually - but this one should take all the
> > commits you locally committed when you worked on your PR and 'transplant'
> > them on top of the main branch.
> >
> > Few things to take care of after:
> >
> > 1. Make sure to rebuild your breeze image:
> >
> > breeze ci-image build
> >
> > 2. Make sure to resync your uv .venv including reinstallation:
> >
> > uv self upgrade
> > uv sync --reinstall
> >
> > This one will update your venv and make sure it gets reinstalled with the
> > new packages and all necessary deps for core airflow.
> >
> > There are quite a few other variants of such sync you should be able to
> > use from now on:
> >
> > *Syncing airflow core minimum dev dependencies *
> >
> > uv sync
> >
> > This one will (after this change) install airflow core + all optional
> > dependencies of airflow + all pre installed providers locally (and their
> > dependencies) . Which means that it should allow to run all `airflow-core`
> > tests. In theory - we still have few tests in airflow that might require
> > other providers - to be cleaned up later. I will modify our CI later to
> > also run using those limited, isolated environments to keep it this way in
> > the future.
> >
> > You should be also able to run tests after regular activation of your venv
> > (. ./.ven/bin/activate) and this is where your IDE should also have your
> > python interpreter set - but uv has this cool `uv run` feature that allows
> > you to run any command with automated activation of the venv:
> >
> > uv run pytest airflow-core/tests/
> >
> >
> > Also this should work out of the box:
> >
> > uv run airflow
> >
> > Go figure :)
> >
> >
> > *Syncing dependencies for particular provider (and other dependent
> > providers)*
> >
> > In the root of Airflow repo
> >
> > uv sync --package apache-airflow-providers-amazon
> >
> > This will sync amazon and all necessary development deps + all the
> > providers that amazon depends on, this way you **should** be able to run
> > all amazon provider tests (including transfers and all others) - what
> > Dennis asked about at the call yesterday.
> >
> > Similarly you can run your tests this way
> >
> > uv run --package apache-airflow-providers-amazon pytest
> > providers/amazon/unit/
> >
> > *Alternative way of syncing provider dependencies *
> >
> > cd providers/amazon
> > uv sync
> >
> > In this case you should be able to also do this:
> >
> > uv run pytest tests/unit/
> >
> > You soon will be able to do the same in `airflow-core` - once the tests
> > that are expecting providers are removed from "airflow-core".
> >
> > cd airflow-core
> > uv sync
> >
> > That's about it. All the rest should not change, Breeze tests,
> > start-airflow etc. should work as usual.
> >
> >
> > *Syncing all dependencies*
> >
> > This is equivalent to what `breeze` image has. I do not really recommend
> > using it daily - syncing venv and swapping dependencies take sub-seconds
> > with *uv, *also you should really treat the .venv in your repo as
> > disposable and something you can easily resync any time.
> >
> > uv sync --all-packages
> >
> > This should allow you to run everything
> >
> > uv run --all-packages pytest 
> >
> > Have fun!
> >
> > I am here and on slack `#contributors` later today. Shoot me with any
> > questions and problems - happy to help (and encourage to help each other
> > there too)
> >
> > *Bonus info*
> >
> > Actually you do not even need to do 'uv sync`. When you use uv run , uv 
> > automatically
> > runs uv sync under the hood (applying the --package switches as
> > appropriate) and you get the latest env resynced automatically !
> >
> > Actually it's even more - you do not need python installed at all when you
> > run `uv run` - uv will download and install (in seconds) the right version
> > of Python for you automatically !
> >
> 

Re: Simple auth manager as default auth manager

[Bishundeo, Rajeshwar]

Awesome job Vincent!!

-- Rajesh 






On 2025-03-21, 3:15 AM, "Amogh Desai" mailto:amoghdesai@gmail.com>> wrote:


CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you can confirm the sender and know the 
content is safe.






AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne 
cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas 
confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le 
contenu ne présente aucun risque.






Good work Vincent!


Happy to see this come in! GO AWAY FAB!




Thanks & Regards,
Amogh Desai




On Fri, Mar 21, 2025 at 12:23 PM Pavankumar Gopidesu <
gopidesupa...@gmail.com > wrote:


> Great work Vincent.
>
> Pavan
>
> On Fri, Mar 21, 2025, 06:46 Shahar Epstein  > wrote:
>
> > Great job Vincent!
> >
> > On Thu, Mar 20, 2025 at 3:18 PM Beck, Vincent
> mailto:vincb...@amazon.com.inva>lid
> > >
> > wrote:
> >
> > > Hi everyone,
> > >
> > > I just merged https://github.com/apache/airflow/pull/47691 
> > >  which sets
> > > SimpleAuthManager as the default auth manager in Airflow. If you pull
> the
> > > latest main branch, Airflow will no longer use the FAB auth Manager by
> > > default but instead use SimpleAuthManager. This is another step towards
> > > removing Flask from Airflow.
> > >
> > > *What changed?*
> > >
> > > Auth managers define authentication (AuthN) and authorization (AuthZ)
> > > logic in Airflow. Switching to SimpleAuthManager means changes in how
> > > authentication and authorization work:
> > > - The FAB login form is no longer used; authentication now follows the
> > > method provided by SimpleAuthManager.
> > > - Pages previously used to manage users and roles (/auth/users/list,
> > > /auth/roles/list, etc.) are no longer available since they are part of
> > the
> > > FAB Auth Manager.
> > > - SimpleAuthManager manages users and roles through a configuration
> file
> > > instead of a web interface.
> > >
> > > For more details on SimpleAuthManager, please refer to the
> documentation:
> > >
> >
> https://github.com/apache/airflow/blob/main/docs/apache-airflow/core-concepts/auth-manager/simple.rst
>  
> 
> > > .
> > > However, SimpleAuthManager is a minimal auth manager designed for
> > > development environments and *should not be used in production*.
> > >
> > > *Using a different auth manager*
> > >
> > > This change only updates the default auth manager, no existing options
> > > have been removed. You can continue using your preferred auth manager,
> > > including FAB, by setting the following in the config `[core]
> > auth_manager
> > > = `. For example, to continue using FAB:: `[core]
> > > auth_manager =
> > > airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager`.
> > >
> > > *Breeze users*
> > >
> > > If you are using Breeze, switching between auth managers is now easier.
> > PR
> > > #47691 introduces a new `--auth-manager` parameter for `breeze
> > > start-airflow`:
> > > - Start Airflow with SimpleAuthManager:: `breeze start-airflow
> > > --auth-manager SimpleAuthManager` (or simply `breeze start-airflow`,
> > since
> > > SimpleAuthManager is now the default)
> > > - Start Airflow with FAB auth manager:: `breeze start-airflow
> > > --auth-manager FabAuthManager`
> > >
> > > Simple auth manager auto generates a random password for all users
> > defined
> > > in the config. These passwords are stored by default in
> > > ``AIRFLOW_HOME/simple_auth_manager_passwords.json.generated``. For
> > > convenience, Breeze predefines two default users:
> > > - "admin" (password: "admin") -> full access
> > > - "viewer" (password: "viewer") -> read-only access
> > >
> > > If you encounter any issues or have concerns about this change, feel
> free
> > > to discuss on Slack or submit a PR to address them.
> > >
> > > Thanks,
> > > Vincent
> > >
> >
>

Re: [ANNOUNCEMENT] airflow-core is there (finally!)

[Kaxil Naik]

Cool

On Fri, 21 Mar 2025 at 20:46, Aritra Basu  wrote:

> Culmination of a great bit of effort Jarek! Great job!! 👏
> --
> Regards,
> Aritra Basu
>
> On Fri, 21 Mar 2025, 7:42 pm Vincent Beck,  wrote:
>
> > It has never been simpler to contribute to Airflow! Awesome job Jarek :)
> >
> > On 2025/03/21 13:50:05 Jarek Potiuk wrote:
> > > Quick additional info - if you have in your repo a 'tests` or 'airflow'
> > > folder remaining in the root of the repo - because you had some extra
> > files
> > > in those (for example generated node_modules)  - you should delete
> those
> > > two directories. They are now unused and any files remaining there can
> > and
> > > *SHOULD* be deleted
> > >
> > > pt., 21 mar 2025, 14:28 użytkownik Jarek Potiuk 
> > napisał:
> > >
> > > > Ok. Now the "airflow-core" change is merged.
> > > >
> > > > Most important - *please rebase all your work now to the latest
> main*.
> > > > Most PR will have conflicts and will require to be rebased anyway,
> but
> > you
> > > > will do you a favour if you do it manually first.
> > > >
> > > > Most likely those rebases will not work from the UI (they will just
> ask
> > > > you to do the rebase manual way and give some hints on how this can
> be
> > done.
> > > >
> > > > If you have apache airflow repo set as remote, (I have 'apache'
> > remote),
> > > > this can be usually done with:
> > > >
> > > > git fetch apache
> > > > git rebase --onto apache/main $(git merge-base)
> > > >
> > > > Of course you have to check it manually - but this one should take
> all
> > the
> > > > commits you locally committed when you worked on your PR and
> > 'transplant'
> > > > them on top of the main branch.
> > > >
> > > > Few things to take care of after:
> > > >
> > > > 1. Make sure to rebuild your breeze image:
> > > >
> > > > breeze ci-image build
> > > >
> > > > 2. Make sure to resync your uv .venv including reinstallation:
> > > >
> > > > uv self upgrade
> > > > uv sync --reinstall
> > > >
> > > > This one will update your venv and make sure it gets reinstalled with
> > the
> > > > new packages and all necessary deps for core airflow.
> > > >
> > > > There are quite a few other variants of such sync you should be able
> to
> > > > use from now on:
> > > >
> > > > *Syncing airflow core minimum dev dependencies *
> > > >
> > > > uv sync
> > > >
> > > > This one will (after this change) install airflow core + all optional
> > > > dependencies of airflow + all pre installed providers locally (and
> > their
> > > > dependencies) . Which means that it should allow to run all
> > `airflow-core`
> > > > tests. In theory - we still have few tests in airflow that might
> > require
> > > > other providers - to be cleaned up later. I will modify our CI later
> to
> > > > also run using those limited, isolated environments to keep it this
> > way in
> > > > the future.
> > > >
> > > > You should be also able to run tests after regular activation of your
> > venv
> > > > (. ./.ven/bin/activate) and this is where your IDE should also have
> > your
> > > > python interpreter set - but uv has this cool `uv run` feature that
> > allows
> > > > you to run any command with automated activation of the venv:
> > > >
> > > > uv run pytest airflow-core/tests/
> > > >
> > > >
> > > > Also this should work out of the box:
> > > >
> > > > uv run airflow
> > > >
> > > > Go figure :)
> > > >
> > > >
> > > > *Syncing dependencies for particular provider (and other dependent
> > > > providers)*
> > > >
> > > > In the root of Airflow repo
> > > >
> > > > uv sync --package apache-airflow-providers-amazon
> > > >
> > > > This will sync amazon and all necessary development deps + all the
> > > > providers that amazon depends on, this way you **should** be able to
> > run
> > > > all amazon provider tests (including transfers and all others) - what
> > > > Dennis asked about at the call yesterday.
> > > >
> > > > Similarly you can run your tests this way
> > > >
> > > > uv run --package apache-airflow-providers-amazon pytest
> > > > providers/amazon/unit/
> > > >
> > > > *Alternative way of syncing provider dependencies *
> > > >
> > > > cd providers/amazon
> > > > uv sync
> > > >
> > > > In this case you should be able to also do this:
> > > >
> > > > uv run pytest tests/unit/
> > > >
> > > > You soon will be able to do the same in `airflow-core` - once the
> tests
> > > > that are expecting providers are removed from "airflow-core".
> > > >
> > > > cd airflow-core
> > > > uv sync
> > > >
> > > > That's about it. All the rest should not change, Breeze tests,
> > > > start-airflow etc. should work as usual.
> > > >
> > > >
> > > > *Syncing all dependencies*
> > > >
> > > > This is equivalent to what `breeze` image has. I do not really
> > recommend
> > > > using it daily - syncing venv and swapping dependencies take
> > sub-seconds
> > > > with *uv, *also you should really treat the .venv in your repo as
> > > > disposable and something you can easily resync any time.
> > > >
> > >

Re: Simple auth manager as default auth manager

[Amogh Desai]

Good work Vincent!

Happy to see this come in! GO AWAY FAB!


Thanks & Regards,
Amogh Desai


On Fri, Mar 21, 2025 at 12:23 PM Pavankumar Gopidesu <
gopidesupa...@gmail.com> wrote:

> Great work Vincent.
>
> Pavan
>
> On Fri, Mar 21, 2025, 06:46 Shahar Epstein  wrote:
>
> > Great job Vincent!
> >
> > On Thu, Mar 20, 2025 at 3:18 PM Beck, Vincent
>  > >
> > wrote:
> >
> > > Hi everyone,
> > >
> > > I just merged https://github.com/apache/airflow/pull/47691 which sets
> > > SimpleAuthManager as the default auth manager in Airflow. If you pull
> the
> > > latest main branch, Airflow will no longer use the FAB auth Manager by
> > > default but instead use SimpleAuthManager. This is another step towards
> > > removing Flask from Airflow.
> > >
> > > *What changed?*
> > >
> > > Auth managers define authentication (AuthN) and authorization (AuthZ)
> > > logic in Airflow. Switching to SimpleAuthManager means changes in how
> > > authentication and authorization work:
> > > - The FAB login form is no longer used; authentication now follows the
> > > method provided by SimpleAuthManager.
> > > - Pages previously used to manage users and roles (/auth/users/list,
> > > /auth/roles/list, etc.) are no longer available since they are part of
> > the
> > > FAB Auth Manager.
> > > - SimpleAuthManager manages users and roles through a configuration
> file
> > > instead of a web interface.
> > >
> > > For more details on SimpleAuthManager, please refer to the
> documentation:
> > >
> >
> https://github.com/apache/airflow/blob/main/docs/apache-airflow/core-concepts/auth-manager/simple.rst
> > > .
> > > However, SimpleAuthManager is a minimal auth manager designed for
> > > development environments and *should not be used in production*.
> > >
> > > *Using a different auth manager*
> > >
> > > This change only updates the default auth manager, no existing options
> > > have been removed. You can continue using your preferred auth manager,
> > > including FAB, by setting the following in the config `[core]
> > auth_manager
> > > = `. For example, to continue using FAB:: `[core]
> > > auth_manager =
> > > airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager`.
> > >
> > > *Breeze users*
> > >
> > > If you are using Breeze, switching between auth managers is now easier.
> > PR
> > > #47691 introduces a new `--auth-manager` parameter for `breeze
> > > start-airflow`:
> > > - Start Airflow with SimpleAuthManager:: `breeze start-airflow
> > > --auth-manager SimpleAuthManager` (or simply `breeze start-airflow`,
> > since
> > > SimpleAuthManager is now the default)
> > > - Start Airflow with FAB auth manager:: `breeze start-airflow
> > > --auth-manager FabAuthManager`
> > >
> > > Simple auth manager auto generates a random password for all users
> > defined
> > > in the config. These passwords are stored by default in
> > > ``AIRFLOW_HOME/simple_auth_manager_passwords.json.generated``. For
> > > convenience, Breeze predefines two default users:
> > > - "admin" (password: "admin") -> full access
> > > - "viewer" (password: "viewer") -> read-only access
> > >
> > > If you encounter any issues or have concerns about this change, feel
> free
> > > to discuss on Slack or submit a PR to address them.
> > >
> > > Thanks,
> > > Vincent
> > >
> >
>

Re: [ANNOUNCE] Apache Airflow Helm Chart version 1.16.0 Released

[Vikram Koka]

Awesome, Thank you Jed!

On Tue, Apr 1, 2025 at 8:17 PM Jed Cunningham 
wrote:

> Dear Airflow community,
>
> I am pleased to announce that we have released Apache Airflow Helm chart
> 1.16.0 🎉 🎊
>
> The source release, as well as the "binary" Helm Chart release, are
> available:
>
> 📦   Official Sources:
>
> https://airflow.apache.org/docs/helm-chart/1.16.0/installing-helm-chart-from-sources.html
> 📦   ArtifactHub:
> https://artifacthub.io/packages/helm/apache-airflow/airflow
> 📚   Docs: https://airflow.apache.org/docs/helm-chart/1.16.0/
> 🚀   Quick Start Installation Guide:
> https://airflow.apache.org/docs/helm-chart/1.16.0/quick-start.html
> 🛠️   Release Notes:
> https://airflow.apache.org/docs/helm-chart/1.16.0/release_notes.html
>
> Thanks to all the contributors who made this possible.
>
> Thanks,
> Jed
>

Re: New committer: Rahul Vats

[Abhishek Bhakat]

Congratulations Rahul 🥳

On Wed, Apr 2, 2025 at 8:13 AM Shahar Epstein  wrote:

> Congratulation Rahul! :)
>
> On Mon, Mar 31, 2025, 21:20 Jed Cunningham 
> wrote:
>
> > The Project Management Committee (PMC) for Apache Airflow
> > has invited Rahul Vats to become a committer and we are pleased
> > to announce that they have accepted.
> >
> > Please join us in welcoming Rahul to their new role and
> > responsibility in our project community.
> >
> > Rahul has had a tremendous impact on Airflow 3, primarily around testing.
> > Thanks Rahul, welcome, it's well deserved!
> >
> > Jed
> > On behalf of the Apache Airflow PMC
> >
>

Re: [ANNOUNCE] UV mandatory tooling and (much nicer) doc building coming

[Buğra Öztürk]

Amazing news! Thanks for the huge effort Jarek! :)

On Wed, 2 Apr 2025, 18:45 Pavankumar Gopidesu, 
wrote:

> That's awesome Jarek, thank you for this :)
>
> Regards,
> Pavan
>
> On Wed, Apr 2, 2025 at 1:09 PM Jarek Potiuk  wrote:
>
> > You might also want to do *docker system prune*  or even *docker system
> > prune --all*  or run *breeze doctor* to clean-up some stale cache,
> images,
> > docker volumes
> >
> > Also IntelliJ/PyCharm users *uv run setup_idea.py* will add some missing
> > directories and regenerate your IntelliJ project configuration.
> >
> >
> >
> >
> >
> > On Wed, Apr 2, 2025 at 1:11 PM Jarek Potiuk  wrote:
> >
> > > Hello here,
> > >
> > > As part of the packaging work - I merged the
> > > https://github.com/apache/airflow/pull/48223
> > >
> > > *TL;DR; Rebase all PRS, rebuild images and uv sync - and
> > > hopefully everything should work as before even if a lot of things
> moved.
> > > Hopefully the move will be largely transparent (except changing
> *include:
> > > in open PRs in docs). *
> > >
> > > *NOTE! UV is now mandatory and a lot of code is gone thanks to that.
> > > Breeze will also refuse to work if uv is not installed.*
> > >
> > > It took a bit of time, but we are in a much more standard and better
> > shape
> > > now - and as a side effect (which was intended but I had to implement
> it
> > as
> > > part of that monster PR to fix documentation) we now have a much
> simpler
> > > (more guidelines are coming) way to iterate on doc building.
> > >
> > > *Few important things first: *
> > >
> > > 1) Make sure to rebase your PRs, Run `breeze image build`, Rnu `uv
> sync`.
> > > Due to the way git handles things - you ** might **  have some dangling
> > > generated directories in your repo and they might cause some problems.
> > Run
> > > "git status" after rebase and see you have some files you need to
> delete
> > > (manually)
> > >
> > > 2) If you are brave enough - you might want to run `breeze doctor` and
> > > cleanup git repo - it should clean all files that should be removed,
> but
> > > also it might remove some of your custom configurations and files you
> > > created,
> > >
> > > 3) Generally everything should work as it worked before with breeze
> (for
> > > example `breeze build-docs` command works as before. But a number of
> > > folders/distributions/code (not airflow nore providers directly) were
> > > moved/updated. For now you can just continue to build docs as before -
> > with
> > > breeze. But simpler/faster ways are coming as follow up.
> > >
> > > 4) If you have some new examples or documentation included in your PRs
> > the
> > > doc build might start falling for you - but this is because `include::`
> > or
> > > `exampleinclude:`  might need to be updated - look at other examples -
> I
> > > fixed the includes in all providers. More explanation in follow-up doc
> > > build improvement PR - in the meantime, feel free to ask on slack or PR
> > for
> > > help.
> > >
> > > *Generated provider_dependencies.json do not need to be updated*
> > >
> > > The "generated/provider_dependencies.json" is no longer committed to
> the
> > > repo - it is .gitignored. We are generating it as-needed on the flight.
> > It
> > > should be automatically regenerated when you run pre-commits locally
> and
> > > when you build the breeze image.
> > >
> > > There might be some cases when we add dependencies and you will need to
> > > regenerate it but that should happen automatically as needed.
> > >
> > > *New, updated folders*
> > >
> > > The change are mostly with these:
> > >
> > > ./dev/pyproject.toml
> > > ./devel-common/pyproject.toml
> > > ./doc
> > > ./docker-stack-docs
> > > ./providers-summary-docs
> > >
> > > *More explanation for distributions/folder changes*
> > >
> > > The dev is now a separate distribution with its own pyproject.toml
> > > dependencies that are used for all the release management and general
> dev
> > > housekeeping. This is different from "devel-common" which is a common
> > > package with a lot of common code reused for tests and builds
> (including
> > > doc builds scripts are using).
> > >
> > > We might want to change names later, as they are confusing but I will
> > > leave that discussion for later when we complete all the isolation
> work -
> > > with those changes I implemented it will be very easy (as opposed to
> how
> > it
> > > was) to move those distributions around - and if we will want to
> > > restructure it again, that will be a very simple move.
> > >
> > > *Improved doc structure*
> > >
> > > This is because we finally made the last step - where the "doc" code is
> > > moved to "devel-common" and we are importing it from there, also each
> > > distribution has it's own "conf.py" and that makes modifying docs
> > building
> > > and our sphinx building scripts MUCH more readable ana mangeable. The
> > "doc"
> > > code now contains just spelling wordlist and README.md explaining where
> > to
> > > look for the documentation.
> > >

Re: [LAZY CONSENSIS] Make git provider pre-installed for Airflow 3

[Jed Cunningham]

I'm slightly against installing by default, actually. Weird from the guy
who added bundle versioning huh? But, if I ignore the short term where we
only have git with bundle versioning, I fully expect there will be more
bundle options that support versioning soon, and forcing git into the mix
just doesn't seem right long term.

This is also just 1 aspect of "versioning" - bundle versioning gives you
"dag code" consistency across a run, but you get dag versioning regardless
of your bundle type. It's helpful, yes, and I'd want it for production. But
not sure it hits the "required" bar.

Re: New committer: Rahul Vats

[Vincent Beck]

Congrats Rahul! Very well deserved!

On 2025/03/31 19:08:09 Shubham Raj wrote:
> Congrats Rahul, well deserved!!
> 
> On Tue, 1 Apr 2025 at 00:33, Vishnu Chilukoori 
> wrote:
> 
> > Congrats Rahul...well deserved!!
> >
> >
> > --
> > Regards,
> > Vishnu Chilukoori
> >
> > On Mon, Mar 31, 2025 at 11:53 AM Idris Adebisi
> >  wrote:
> >
> > >  Congratulations, Rahul!
> > >
> > > On Monday, March 31, 2025 at 07:45:27 PM GMT+1, Ambika Garg <
> > > ambikagarg1...@gmail.com> wrote:
> > >
> > >  Congratulations Rahul!!
> > > On Mon, Mar 31, 2025 at 2:43 PM Ankit Chaurasia 
> > > wrote:
> > >
> > > > Congratulations, Rahul! Well deserved.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Apr 1, 2025 at 12:16 AM Constance Martineau
> > > >  wrote:
> > > >
> > > > > Congrats Rahul! Well deserved :)
> > > > >
> > > > > On Mon, Mar 31, 2025 at 2:28 PM Oliveira, Niko
> > > >  > > > > >
> > > > > wrote:
> > > > >
> > > > > > Congrats Rahul, great work!
> > > > > >
> > > > > > 
> > > > > > From: Jed Cunningham 
> > > > > > Sent: Monday, March 31, 2025 11:19:53 AM
> > > > > > To: dev@airflow.apache.org
> > > > > > Subject: [EXT] New committer: Rahul Vats
> > > > > >
> > > > > > CAUTION: This email originated from outside of the organization. Do
> > > not
> > > > > > click links or open attachments unless you can confirm the sender
> > and
> > > > > know
> > > > > > the content is safe.
> > > > > >
> > > > > >
> > > > > >
> > > > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur
> > > > externe.
> > > > > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous
> > ne
> > > > > pouvez
> > > > > > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas
> > > certain
> > > > > que
> > > > > > le contenu ne présente aucun risque.
> > > > > >
> > > > > >
> > > > > >
> > > > > > The Project Management Committee (PMC) for Apache Airflow
> > > > > > has invited Rahul Vats to become a committer and we are pleased
> > > > > > to announce that they have accepted.
> > > > > >
> > > > > > Please join us in welcoming Rahul to their new role and
> > > > > > responsibility in our project community.
> > > > > >
> > > > > > Rahul has had a tremendous impact on Airflow 3, primarily around
> > > > testing.
> > > > > > Thanks Rahul, welcome, it's well deserved!
> > > > > >
> > > > > > Jed
> > > > > > On behalf of the Apache Airflow PMC
> > > > > >
> > > > >
> > > >
> > >
> >
> 

-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

Re: New committer: Rahul Vats

[Hemkumar Chheda]

Congratulations Rahul! Well Deserved 🥳🎉

Best Regards,
Hemkumar

> On 1 Apr 2025, at 6:37 AM, Wei Lee  wrote:
> 
> Congratulations!
> 
> Best,
> Wei
> 
>> On Apr 1, 2025, at 8:36 AM, Zhe You Liu  wrote:
>> 
>> Congrats Rahul, well deserved!
>> 
>> On Tue, Apr 1, 2025 at 9:28 AM Ephraim Anierobi 
>> wrote:
>> 
>>> Congratulations Rahul! Well deserved
>>> 
>>> On Tue, 1 Apr 2025 at 01:27, Pierre Jeambrun 
>>> wrote:
>>> 
 Amazing work Rahul, congratulations.
 
 On Mon 31 Mar 2025 at 23:14, Pavankumar Gopidesu <
>>> gopidesupa...@gmail.com>
 wrote:
 
> Woohoo, Congratulations Rahul 🎉🎉
> 
> Pavan.
> 
> On Mon, Mar 31, 2025 at 9:17 PM Pankaj Koti
>  wrote:
> 
>> Many congratulations Rahul! Very happy for you and well deserved 🎉🎉
>> 
>> On Tue, 1 Apr, 2025, 01:17 Buğra Öztürk, 
> wrote:
>> 
>>> Amazing news! Congratulations Rahul! Well deserved!
>>> 
>>> On Mon, Mar 31, 2025 at 9:14 PM Vincent Beck 
>> wrote:
>>> 
 Congrats Rahul! Very well deserved!
 
 On 2025/03/31 19:08:09 Shubham Raj wrote:
> Congrats Rahul, well deserved!!
> 
> On Tue, 1 Apr 2025 at 00:33, Vishnu Chilukoori <
 vish.chiluko...@gmail.com>
> wrote:
> 
>> Congrats Rahul...well deserved!!
>> 
>> 
>> --
>> Regards,
>> Vishnu Chilukoori
>> 
>> On Mon, Mar 31, 2025 at 11:53 AM Idris Adebisi
>>  wrote:
>> 
>>> Congratulations, Rahul!
>>> 
>>>   On Monday, March 31, 2025 at 07:45:27 PM GMT+1, Ambika
> Garg <
>>> ambikagarg1...@gmail.com> wrote:
>>> 
>>> Congratulations Rahul!!
>>> On Mon, Mar 31, 2025 at 2:43 PM Ankit Chaurasia <
>>> sunank...@gmail.com
> 
>>> wrote:
>>> 
 Congratulations, Rahul! Well deserved.
 
 
 
 
 
 
 
 On Tue, Apr 1, 2025 at 12:16 AM Constance Martineau
  wrote:
 
> Congrats Rahul! Well deserved :)
> 
> On Mon, Mar 31, 2025 at 2:28 PM Oliveira, Niko
 > 
> wrote:
> 
>> Congrats Rahul, great work!
>> 
>> 
>> From: Jed Cunningham 
>> Sent: Monday, March 31, 2025 11:19:53 AM
>> To: dev@airflow.apache.org
>> Subject: [EXT] New committer: Rahul Vats
>> 
>> CAUTION: This email originated from outside of the
 organization. Do
>>> not
>> click links or open attachments unless you can
>>> confirm
> the
 sender
>> and
> know
>> the content is safe.
>> 
>> 
>> 
>> AVERTISSEMENT: Ce courrier électronique provient d’un
 expéditeur
 externe.
>> Ne cliquez sur aucun lien et n’ouvrez aucune pièce
 jointe
>> si
 vous
>> ne
> pouvez
>> pas confirmer l’identité de l’expéditeur et si vous
> n’êtes
>>> pas
>>> certain
> que
>> le contenu ne présente aucun risque.
>> 
>> 
>> 
>> The Project Management Committee (PMC) for Apache
 Airflow
>> has invited Rahul Vats to become a committer and we
>>> are
>>> pleased
>> to announce that they have accepted.
>> 
>> Please join us in welcoming Rahul to their new role
>>> and
>> responsibility in our project community.
>> 
>> Rahul has had a tremendous impact on Airflow 3,
 primarily
 around
 testing.
>> Thanks Rahul, welcome, it's well deserved!
>> 
>> Jed
>> On behalf of the Apache Airflow PMC
>> 
> 
 
>>> 
>> 
> 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
 For additional commands, e-mail: dev-h...@airflow.apache.org
 
 
>>> 
>>> --
>>> Bugra Ozturk
>>> 
>> 
> 
 
>>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

Re: New committer: Rahul Vats

[Jarek Potiuk]

Wooohooo! Congrats ! Well deserved!

On Mon, Mar 31, 2025 at 8:53 PM Idris Adebisi
 wrote:

>  Congratulations, Rahul!
>
> On Monday, March 31, 2025 at 07:45:27 PM GMT+1, Ambika Garg <
> ambikagarg1...@gmail.com> wrote:
>
>  Congratulations Rahul!!
> On Mon, Mar 31, 2025 at 2:43 PM Ankit Chaurasia 
> wrote:
>
> > Congratulations, Rahul! Well deserved.
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Apr 1, 2025 at 12:16 AM Constance Martineau
> >  wrote:
> >
> > > Congrats Rahul! Well deserved :)
> > >
> > > On Mon, Mar 31, 2025 at 2:28 PM Oliveira, Niko
> >  > > >
> > > wrote:
> > >
> > > > Congrats Rahul, great work!
> > > >
> > > > 
> > > > From: Jed Cunningham 
> > > > Sent: Monday, March 31, 2025 11:19:53 AM
> > > > To: dev@airflow.apache.org
> > > > Subject: [EXT] New committer: Rahul Vats
> > > >
> > > > CAUTION: This email originated from outside of the organization. Do
> not
> > > > click links or open attachments unless you can confirm the sender and
> > > know
> > > > the content is safe.
> > > >
> > > >
> > > >
> > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur
> > externe.
> > > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne
> > > pouvez
> > > > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas
> certain
> > > que
> > > > le contenu ne présente aucun risque.
> > > >
> > > >
> > > >
> > > > The Project Management Committee (PMC) for Apache Airflow
> > > > has invited Rahul Vats to become a committer and we are pleased
> > > > to announce that they have accepted.
> > > >
> > > > Please join us in welcoming Rahul to their new role and
> > > > responsibility in our project community.
> > > >
> > > > Rahul has had a tremendous impact on Airflow 3, primarily around
> > testing.
> > > > Thanks Rahul, welcome, it's well deserved!
> > > >
> > > > Jed
> > > > On behalf of the Apache Airflow PMC
> > > >
> > >
> >
>

Re: Airflow Mentors for Summer 2025 MLH Fellowship

[kalyan reddy]

I am interested to mentor.

Thanks

From: Jarek Potiuk 
Sent: 05 April 2025 12:41
To: dev@airflow.apache.org 
Cc: al...@majorleaguehacking.com 
Subject: Re: Airflow Mentors for Summer 2025 MLH Fellowship

Same here as Dennis and Amogh . This is good stuff :). But with Airflow 3/
Security work, hard for me to commit - but happy to help with code reviews
and such :)

On Sat, Apr 5, 2025 at 7:47 AM Amogh Desai  wrote:

> Hey Everyone,
>
> I also worked with Alex and his team during the fall of 2023 and it was an
> amazing experience.
>
> Mentoring some young college folks into a project foreign to them is very
> rewarding both for them as well as
> for the mentor. As a mentor, i learnt a lot during this process due to the
> beginner doubts and issues the mentees
> ran into which we often ignore as solving such issues seems trivial to us.
> This led to a lot of improvements
> in breeze as well during that time.
>
> Similar to Dennis, I won't be able to commit the time required (which isn't
> a lot btw) and I also want to give this
> chance to others as well :)
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Sat, Apr 5, 2025 at 2:32 AM Ferruzzi, Dennis
> 
> wrote:
>
> > Hey.  As Alex mentioned, I've worked with them for a couple of cohorts.
> > The only reason I'm not doing the next one is because I have a lot going
> on
> > in Real Life this summer and won't be able to commit the time.  If anyone
> > is interested but wants to chat about what it's like, feel free to hit me
> > up on the Slack channel.
> >
> >
> >  - ferruzzi
> >
> >
> > 
> > From: karan alang 
> > Sent: Thursday, April 3, 2025 4:38 PM
> > To: dev@airflow.apache.org; al...@majorleaguehacking.com
> > Subject: RE: [EXT] Airflow Mentors for Summer 2025 MLH Fellowship
> >
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you can confirm the sender and
> know
> > the content is safe.
> >
> >
> >
> > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe.
> > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne
> pouvez
> > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain
> que
> > le contenu ne présente aucun risque.
> >
> >
> >
> > Hi Alex,
> >
> > I'm happy to help out with this.
> >
> > regds,
> > Karan Alang
> >
> >
> > On Thu, Apr 3, 2025 at 4:13 PM Alex Gornet
> >  wrote:
> >
> > > Hi Airflow team,
> > >
> > > I'm Alex Gornet, a Partner Success Manager at Major League Hacking.
> Here
> > at
> > > MLH we run an Open Source Fellowship program
> > >  that functions like an internship
> > for
> > > student developers to contribute to open source projects. *Fellows from
> > our
> > > program have successfully contributed to Airflow since Fall 2024. *
> > >
> > > This year Royal Bank of Canada is sponsoring some seats in the program,
> > and
> > > they'd like their Fellows to contribute to Airflow as a way to give
> back
> > to
> > > the community. *With the recent release of Airflow 3.0, these Fellows
> > would
> > > be great candidates for tackling the backlog of bugs / issues following
> > the
> > > transition. *
> > >
> > > *Right now, we're looking for maintainers / core contributors to
> provide
> > > technical mentorship to the students*, so we'd love your help to
> > identify 2
> > > maintainers / core contributors (or more!) who could take lead here and
> > > support us bringing on some great new contributors.
> > >
> > >- *The program runs from May 19th to August 8th*, and we'd ask for
> ~2
> > >hours of your time each week.
> > >
> > > *If this is something you'd be interested in helping out with, you can
> > > simply reply to this email or reach out to me directly at
> > > al...@majorleaguehacking.com * — since
> > we're
> > > not too far out from program launch, the sooner you can let us know the
> > > better!
> > >
> > > If you have any questions about the program or want to chat more about
> > it,
> > > let me know and I'm happy to find time. You can also reach out to
> Dennis
> > > Ferruzzi who has mentored the last couple of cohorts to hear more about
> > his
> > > mentoring experience.
> > >
> > > Best,
> > > Alex
> > >
> >
>

Re: Simple auth manager as default auth manager

[Buğra Öztürk]

Great work Vincent! Thanks for the details!

On Fri, Mar 21, 2025 at 2:49 PM Bishundeo, Rajeshwar
 wrote:

> Awesome job Vincent!!
>
> -- Rajesh
>
>
>
>
>
>
> On 2025-03-21, 3:15 AM, "Amogh Desai"  amoghdesai@gmail.com>> wrote:
>
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
>
>
>
>
> AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe.
> Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez
> pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que
> le contenu ne présente aucun risque.
>
>
>
>
>
>
> Good work Vincent!
>
>
> Happy to see this come in! GO AWAY FAB!
>
>
>
>
> Thanks & Regards,
> Amogh Desai
>
>
>
>
> On Fri, Mar 21, 2025 at 12:23 PM Pavankumar Gopidesu <
> gopidesupa...@gmail.com > wrote:
>
>
> > Great work Vincent.
> >
> > Pavan
> >
> > On Fri, Mar 21, 2025, 06:46 Shahar Epstein  sha...@apache.org>> wrote:
> >
> > > Great job Vincent!
> > >
> > > On Thu, Mar 20, 2025 at 3:18 PM Beck, Vincent
> > mailto:vincb...@amazon.com.inva>lid
> > > >
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > I just merged https://github.com/apache/airflow/pull/47691 <
> https://github.com/apache/airflow/pull/47691> which sets
> > > > SimpleAuthManager as the default auth manager in Airflow. If you pull
> > the
> > > > latest main branch, Airflow will no longer use the FAB auth Manager
> by
> > > > default but instead use SimpleAuthManager. This is another step
> towards
> > > > removing Flask from Airflow.
> > > >
> > > > *What changed?*
> > > >
> > > > Auth managers define authentication (AuthN) and authorization (AuthZ)
> > > > logic in Airflow. Switching to SimpleAuthManager means changes in how
> > > > authentication and authorization work:
> > > > - The FAB login form is no longer used; authentication now follows
> the
> > > > method provided by SimpleAuthManager.
> > > > - Pages previously used to manage users and roles (/auth/users/list,
> > > > /auth/roles/list, etc.) are no longer available since they are part
> of
> > > the
> > > > FAB Auth Manager.
> > > > - SimpleAuthManager manages users and roles through a configuration
> > file
> > > > instead of a web interface.
> > > >
> > > > For more details on SimpleAuthManager, please refer to the
> > documentation:
> > > >
> > >
> >
> https://github.com/apache/airflow/blob/main/docs/apache-airflow/core-concepts/auth-manager/simple.rst
> <
> https://github.com/apache/airflow/blob/main/docs/apache-airflow/core-concepts/auth-manager/simple.rst
> >
> > > > .
> > > > However, SimpleAuthManager is a minimal auth manager designed for
> > > > development environments and *should not be used in production*.
> > > >
> > > > *Using a different auth manager*
> > > >
> > > > This change only updates the default auth manager, no existing
> options
> > > > have been removed. You can continue using your preferred auth
> manager,
> > > > including FAB, by setting the following in the config `[core]
> > > auth_manager
> > > > = `. For example, to continue using FAB:: `[core]
> > > > auth_manager =
> > > > airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager`.
> > > >
> > > > *Breeze users*
> > > >
> > > > If you are using Breeze, switching between auth managers is now
> easier.
> > > PR
> > > > #47691 introduces a new `--auth-manager` parameter for `breeze
> > > > start-airflow`:
> > > > - Start Airflow with SimpleAuthManager:: `breeze start-airflow
> > > > --auth-manager SimpleAuthManager` (or simply `breeze start-airflow`,
> > > since
> > > > SimpleAuthManager is now the default)
> > > > - Start Airflow with FAB auth manager:: `breeze start-airflow
> > > > --auth-manager FabAuthManager`
> > > >
> > > > Simple auth manager auto generates a random password for all users
> > > defined
> > > > in the config. These passwords are stored by default in
> > > > ``AIRFLOW_HOME/simple_auth_manager_passwords.json.generated``. For
> > > > convenience, Breeze predefines two default users:
> > > > - "admin" (password: "admin") -> full access
> > > > - "viewer" (password: "viewer") -> read-only access
> > > >
> > > > If you encounter any issues or have concerns about this change, feel
> > free
> > > > to discuss on Slack or submit a PR to address them.
> > > >
> > > > Thanks,
> > > > Vincent
> > > >
> > >
> >
>
>
>
>

-- 
Bugra Ozturk

Re: Should we drop support for pre_execute & post_execute for AF 3.0

[Kaxil Naik]

@tamara : Correct, we are now proposing to remove overriding the pre/post
execute

>Quick question if I am understanding the proposed change correctly.


What you want to remove is overriding the pre/post execute when creating
> custom operators:
>
> class MyOperator(BaseOperator):
>
> ...
>
> def pre_execute(self, context):   # This would break?
> 
> def post_execute(self, context):   # And this as well?
> But keep the (currently experimental) use of the pre_execute and
> post_execute parameters (I've only used post_execute before for similar
> reasons as TP posted, interacting with outlets assets)


On Sat, 29 Mar 2025 at 18:23, Kaxil Naik  wrote:

> No, @run_if / @skip_if uses pre_execute from task argument [1] not the the
> method and is just a syntactic sugar. You can also do the following as an
> example:
>
> ```
> def skip_at_random(context):
> if randint(0, 1) == 0:
> raise AirflowSkipException()
>
> t2 = BashOperator(task_id='conditional2', pre_execute=skip_at_random,
> dag=dag, bash_command="airflow version")
> ```
>
> [1]:
> https://github.com/apache/airflow/blob/8c3a30e3ffc3f114c1d2cc3e6e109f4d9e29ca8b/airflow-core/src/airflow/decorators/condition.py#L57-L59
>
> On Sat, 29 Mar 2025 at 05:09, Matthew Block 
> wrote:
>
>> Would this also break @run_if/@skip_if decorators?
>>
>> Best,
>> Matt Block
>>
>> > On Mar 28, 2025, at 3:44 PM, Tamara Fingerlin
>>  wrote:
>> >
>> > Hey :)
>> >
>> > Quick question if I am understanding the proposed change correctly.
>> >
>> > What you want to remove is overriding the pre/post execute when creating
>> > custom operators:
>> >
>> > class MyOperator(BaseOperator):
>> >...
>> >def pre_execute(self, context):   # This would break?
>> >
>> >
>> >def post_execute(self, context):   # And this as well?
>> >
>> >
>> > But keep the (currently experimental) use of the pre_execute and
>> > post_execute parameters (I've only used post_execute before for similar
>> > reasons as TP posted, interacting with outlets assets)
>> >
>> >BashOperator(
>> >task_id='hello_world',
>> >bash_command='sleep 5',
>> >pre_execute=lambda context: print("Pre-execute function
>> called!"),
>> > # this would still work?
>> >post_execute=lambda context: print("Post-execute function
>> > called!"),   # this would be supposed to still work (it does not rn 😅)
>> >)
>> >
>> > The one situation I am worried about here is larger teams/orgs using pre
>> > and post execute to standardize custom operators. For example team A
>> writes
>> > OurCompanyDatabaseBaseOperator that has a pre_execute and post_execute
>> with
>> > mandatory business logic and team B is allowed to write custom
>> operators on
>> > top of that but only override execute.
>> > I assume this would break?
>> >
>> >
>> >> On Fri, Mar 28, 2025 at 9:32 PM Jarek Potiuk  wrote:
>> >>
>> >> I think the current proposal is to remove the pre/post in the Base
>> Operator
>> >> class (and overridability) and leave passing pre/post as constructor
>> >> arguments..
>> >>
>> >>> On Fri, Mar 28, 2025 at 9:20 PM Bolke de Bruin 
>> wrote:
>> >>>
>> >>> Just one thing - the pre / post mechanisms are executed in-process of
>> the
>> >>> task rather than the DAG. So they are not equal to setup/teardown. Are
>> >> you
>> >>> proposing to remove the argument or the whole thing?
>> >>>
>> >>> B.
>> >>>
>> >>>
>> >>>
>>  On Fri, 28 Mar 2025 at 20:58, Jarek Potiuk  wrote:
>> >>>
>>  Indeed. Post/pre overriding in sub-classes should go away (and we
>> could
>>  even likely implement a ruff rule to auto-fix those if someone has a
>> >>> custom
>>  executor. Sounds like 100% doable
>> 
>>  But passing them as "cross-cutting concerns" via callable in a
>> >>> constructor
>>  is pretty useful and not easily fixable for back-compatibilty
>> 
>>  J.
>> 
>>  On Fri, Mar 28, 2025 at 6:14 PM Kaxil Naik 
>> >> wrote:
>> 
>> >> I think the ability of overriding pre_execute and post_execute in a
>> > subclass can definitely go away. They are practically useles; you
>> can
>>  just
>> > put everything in execute, which always needs to exist in a
>> >>> BaseOperator
>> > subclass anyway.
>> >
>> > Yeah I am fine with removing that then. Anyone disagrees?
>> >
>> > On Fri, 28 Mar 2025 at 20:36, Michał Modras <
>> michalmod...@google.com
>> > .invalid>
>> > wrote:
>> >
>> >> I'd prefer a world without separate pre_execute and post_execute
>> > functions
>> >> - as pointed out in the PR, they make reasoning about DAGs more
>>  complex,
>> >> and can be error prone.
>> >>
>> >> Having said that, I know there are multiple users relying on these
>> >> functionalities, so I'll bring up my usual - another breaking
>> >> change
>> >>> -
>> >> another obstacle to the AF3 adoption argument.
>> >>
>> >> And as for relying on operators vs. PythonOpe

Re: [ANNOUNCEMENT] airflow-core is there (finally!)

[Aritra Basu]

Culmination of a great bit of effort Jarek! Great job!! 👏
--
Regards,
Aritra Basu

On Fri, 21 Mar 2025, 7:42 pm Vincent Beck,  wrote:

> It has never been simpler to contribute to Airflow! Awesome job Jarek :)
>
> On 2025/03/21 13:50:05 Jarek Potiuk wrote:
> > Quick additional info - if you have in your repo a 'tests` or 'airflow'
> > folder remaining in the root of the repo - because you had some extra
> files
> > in those (for example generated node_modules)  - you should delete those
> > two directories. They are now unused and any files remaining there can
> and
> > *SHOULD* be deleted
> >
> > pt., 21 mar 2025, 14:28 użytkownik Jarek Potiuk 
> napisał:
> >
> > > Ok. Now the "airflow-core" change is merged.
> > >
> > > Most important - *please rebase all your work now to the latest main*.
> > > Most PR will have conflicts and will require to be rebased anyway, but
> you
> > > will do you a favour if you do it manually first.
> > >
> > > Most likely those rebases will not work from the UI (they will just ask
> > > you to do the rebase manual way and give some hints on how this can be
> done.
> > >
> > > If you have apache airflow repo set as remote, (I have 'apache'
> remote),
> > > this can be usually done with:
> > >
> > > git fetch apache
> > > git rebase --onto apache/main $(git merge-base)
> > >
> > > Of course you have to check it manually - but this one should take all
> the
> > > commits you locally committed when you worked on your PR and
> 'transplant'
> > > them on top of the main branch.
> > >
> > > Few things to take care of after:
> > >
> > > 1. Make sure to rebuild your breeze image:
> > >
> > > breeze ci-image build
> > >
> > > 2. Make sure to resync your uv .venv including reinstallation:
> > >
> > > uv self upgrade
> > > uv sync --reinstall
> > >
> > > This one will update your venv and make sure it gets reinstalled with
> the
> > > new packages and all necessary deps for core airflow.
> > >
> > > There are quite a few other variants of such sync you should be able to
> > > use from now on:
> > >
> > > *Syncing airflow core minimum dev dependencies *
> > >
> > > uv sync
> > >
> > > This one will (after this change) install airflow core + all optional
> > > dependencies of airflow + all pre installed providers locally (and
> their
> > > dependencies) . Which means that it should allow to run all
> `airflow-core`
> > > tests. In theory - we still have few tests in airflow that might
> require
> > > other providers - to be cleaned up later. I will modify our CI later to
> > > also run using those limited, isolated environments to keep it this
> way in
> > > the future.
> > >
> > > You should be also able to run tests after regular activation of your
> venv
> > > (. ./.ven/bin/activate) and this is where your IDE should also have
> your
> > > python interpreter set - but uv has this cool `uv run` feature that
> allows
> > > you to run any command with automated activation of the venv:
> > >
> > > uv run pytest airflow-core/tests/
> > >
> > >
> > > Also this should work out of the box:
> > >
> > > uv run airflow
> > >
> > > Go figure :)
> > >
> > >
> > > *Syncing dependencies for particular provider (and other dependent
> > > providers)*
> > >
> > > In the root of Airflow repo
> > >
> > > uv sync --package apache-airflow-providers-amazon
> > >
> > > This will sync amazon and all necessary development deps + all the
> > > providers that amazon depends on, this way you **should** be able to
> run
> > > all amazon provider tests (including transfers and all others) - what
> > > Dennis asked about at the call yesterday.
> > >
> > > Similarly you can run your tests this way
> > >
> > > uv run --package apache-airflow-providers-amazon pytest
> > > providers/amazon/unit/
> > >
> > > *Alternative way of syncing provider dependencies *
> > >
> > > cd providers/amazon
> > > uv sync
> > >
> > > In this case you should be able to also do this:
> > >
> > > uv run pytest tests/unit/
> > >
> > > You soon will be able to do the same in `airflow-core` - once the tests
> > > that are expecting providers are removed from "airflow-core".
> > >
> > > cd airflow-core
> > > uv sync
> > >
> > > That's about it. All the rest should not change, Breeze tests,
> > > start-airflow etc. should work as usual.
> > >
> > >
> > > *Syncing all dependencies*
> > >
> > > This is equivalent to what `breeze` image has. I do not really
> recommend
> > > using it daily - syncing venv and swapping dependencies take
> sub-seconds
> > > with *uv, *also you should really treat the .venv in your repo as
> > > disposable and something you can easily resync any time.
> > >
> > > uv sync --all-packages
> > >
> > > This should allow you to run everything
> > >
> > > uv run --all-packages pytest 
> > >
> > > Have fun!
> > >
> > > I am here and on slack `#contributors` later today. Shoot me with any
> > > questions and problems - happy to help (and encourage to help each
> other
> > > there too)
> > >
> > > *Bonus info*
> > >
> > 

Re: New committer: Rahul Vats

[Kunal Bhattacharya]

Congratulations Rahul, very well deserved :)

Regards,
Kunal Bhattacharya

On Tue, Apr 1, 2025 at 11:04 AM Amogh Desai 
wrote:

> Congratulations Rahul!
>
> I have first hand seen the impact you create in Airflow and the way you
> drive
> testing efforts. Kudos to you.
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Tue, Apr 1, 2025 at 9:24 AM Phani Kumar
>  wrote:
>
> > Congratulations Rahul 🎊
> >
> > On Tue, 1 Apr, 2025, 08:56 Aritra Basu, 
> wrote:
> >
> > > Congrats Rahul, great job!
> > > --
> > > Regards,
> > > Aritra Basu
> > >
> > > On Tue, 1 Apr 2025, 8:42 am kalyan reddy, 
> wrote:
> > >
> > > > Congratulations Rahul! Thanks for your amazing work. Well deserved !!
> > > > 
> > > > From: Hemkumar Chheda 
> > > > Sent: 01 April 2025 07:12
> > > > To: dev@airflow.apache.org 
> > > > Subject: Re: New committer: Rahul Vats
> > > >
> > > > Congratulations Rahul! Well Deserved 🥳🎉
> > > >
> > > > Best Regards,
> > > > Hemkumar
> > > >
> > > > > On 1 Apr 2025, at 6:37 AM, Wei Lee  wrote:
> > > > >
> > > > > Congratulations!
> > > > >
> > > > > Best,
> > > > > Wei
> > > > >
> > > > >> On Apr 1, 2025, at 8:36 AM, Zhe You Liu 
> > wrote:
> > > > >>
> > > > >> Congrats Rahul, well deserved!
> > > > >>
> > > > >> On Tue, Apr 1, 2025 at 9:28 AM Ephraim Anierobi <
> > > > ephraimanier...@gmail.com>
> > > > >> wrote:
> > > > >>
> > > > >>> Congratulations Rahul! Well deserved
> > > > >>>
> > > > >>> On Tue, 1 Apr 2025 at 01:27, Pierre Jeambrun <
> > pierrejb...@gmail.com>
> > > > >>> wrote:
> > > > >>>
> > > >  Amazing work Rahul, congratulations.
> > > > 
> > > >  On Mon 31 Mar 2025 at 23:14, Pavankumar Gopidesu <
> > > > >>> gopidesupa...@gmail.com>
> > > >  wrote:
> > > > 
> > > > > Woohoo, Congratulations Rahul 🎉🎉
> > > > >
> > > > > Pavan.
> > > > >
> > > > > On Mon, Mar 31, 2025 at 9:17 PM Pankaj Koti
> > > > >  wrote:
> > > > >
> > > > >> Many congratulations Rahul! Very happy for you and well
> deserved
> > > > 🎉🎉
> > > > >>
> > > > >> On Tue, 1 Apr, 2025, 01:17 Buğra Öztürk, <
> > ozturkbugr...@gmail.com
> > > >
> > > > > wrote:
> > > > >>
> > > > >>> Amazing news! Congratulations Rahul! Well deserved!
> > > > >>>
> > > > >>> On Mon, Mar 31, 2025 at 9:14 PM Vincent Beck <
> > > vincb...@apache.org>
> > > > >> wrote:
> > > > >>>
> > > >  Congrats Rahul! Very well deserved!
> > > > 
> > > >  On 2025/03/31 19:08:09 Shubham Raj wrote:
> > > > > Congrats Rahul, well deserved!!
> > > > >
> > > > > On Tue, 1 Apr 2025 at 00:33, Vishnu Chilukoori <
> > > >  vish.chiluko...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Congrats Rahul...well deserved!!
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Regards,
> > > > >> Vishnu Chilukoori
> > > > >>
> > > > >> On Mon, Mar 31, 2025 at 11:53 AM Idris Adebisi
> > > > >>  wrote:
> > > > >>
> > > > >>> Congratulations, Rahul!
> > > > >>>
> > > > >>>   On Monday, March 31, 2025 at 07:45:27 PM GMT+1, Ambika
> > > > > Garg <
> > > > >>> ambikagarg1...@gmail.com> wrote:
> > > > >>>
> > > > >>> Congratulations Rahul!!
> > > > >>> On Mon, Mar 31, 2025 at 2:43 PM Ankit Chaurasia <
> > > > >>> sunank...@gmail.com
> > > > >
> > > > >>> wrote:
> > > > >>>
> > > >  Congratulations, Rahul! Well deserved.
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  On Tue, Apr 1, 2025 at 12:16 AM Constance Martineau
> > > >   wrote:
> > > > 
> > > > > Congrats Rahul! Well deserved :)
> > > > >
> > > > > On Mon, Mar 31, 2025 at 2:28 PM Oliveira, Niko
> > > >   > > > >>
> > > > > wrote:
> > > > >
> > > > >> Congrats Rahul, great work!
> > > > >>
> > > > >> 
> > > > >> From: Jed Cunningham 
> > > > >> Sent: Monday, March 31, 2025 11:19:53 AM
> > > > >> To: dev@airflow.apache.org
> > > > >> Subject: [EXT] New committer: Rahul Vats
> > > > >>
> > > > >> CAUTION: This email originated from outside of the
> > > >  organization. Do
> > > > >>> not
> > > > >> click links or open attachments unless you can
> > > > >>> confirm
> > > > > the
> > > >  sender
> > > > >> and
> > > > > know
> > > > >> the content is safe.
> > > > >>
> > > > >>
> > > > >>
> > > > >> AVERTISSEMENT: Ce courrier électronique provient d’un
> > > >  expéditeur
> > > >  exte

Re: Simple auth manager as default auth manager

[Pavankumar Gopidesu]

Great work Vincent.

Pavan

On Fri, Mar 21, 2025, 06:46 Shahar Epstein  wrote:

> Great job Vincent!
>
> On Thu, Mar 20, 2025 at 3:18 PM Beck, Vincent  >
> wrote:
>
> > Hi everyone,
> >
> > I just merged https://github.com/apache/airflow/pull/47691 which sets
> > SimpleAuthManager as the default auth manager in Airflow. If you pull the
> > latest main branch, Airflow will no longer use the FAB auth Manager by
> > default but instead use SimpleAuthManager. This is another step towards
> > removing Flask from Airflow.
> >
> > *What changed?*
> >
> > Auth managers define authentication (AuthN) and authorization (AuthZ)
> > logic in Airflow. Switching to SimpleAuthManager means changes in how
> > authentication and authorization work:
> > - The FAB login form is no longer used; authentication now follows the
> > method provided by SimpleAuthManager.
> > - Pages previously used to manage users and roles (/auth/users/list,
> > /auth/roles/list, etc.) are no longer available since they are part of
> the
> > FAB Auth Manager.
> > - SimpleAuthManager manages users and roles through a configuration file
> > instead of a web interface.
> >
> > For more details on SimpleAuthManager, please refer to the documentation:
> >
> https://github.com/apache/airflow/blob/main/docs/apache-airflow/core-concepts/auth-manager/simple.rst
> > .
> > However, SimpleAuthManager is a minimal auth manager designed for
> > development environments and *should not be used in production*.
> >
> > *Using a different auth manager*
> >
> > This change only updates the default auth manager, no existing options
> > have been removed. You can continue using your preferred auth manager,
> > including FAB, by setting the following in the config `[core]
> auth_manager
> > = `. For example, to continue using FAB:: `[core]
> > auth_manager =
> > airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager`.
> >
> > *Breeze users*
> >
> > If you are using Breeze, switching between auth managers is now easier.
> PR
> > #47691 introduces a new `--auth-manager` parameter for `breeze
> > start-airflow`:
> > - Start Airflow with SimpleAuthManager:: `breeze start-airflow
> > --auth-manager SimpleAuthManager` (or simply `breeze start-airflow`,
> since
> > SimpleAuthManager is now the default)
> > - Start Airflow with FAB auth manager:: `breeze start-airflow
> > --auth-manager FabAuthManager`
> >
> > Simple auth manager auto generates a random password for all users
> defined
> > in the config. These passwords are stored by default in
> > ``AIRFLOW_HOME/simple_auth_manager_passwords.json.generated``. For
> > convenience, Breeze predefines two default users:
> > - "admin" (password: "admin") -> full access
> > - "viewer" (password: "viewer") -> read-only access
> >
> > If you encounter any issues or have concerns about this change, feel free
> > to discuss on Slack or submit a PR to address them.
> >
> > Thanks,
> > Vincent
> >
>

[ANNOUNCEMENT] airflow-core is there (finally!)

[Jarek Potiuk]

Ok. Now the "airflow-core" change is merged.

Most important - *please rebase all your work now to the latest main*. Most
PR will have conflicts and will require to be rebased anyway, but you will
do you a favour if you do it manually first.

Most likely those rebases will not work from the UI (they will just ask you
to do the rebase manual way and give some hints on how this can be done.

If you have apache airflow repo set as remote, (I have 'apache' remote),
this can be usually done with:

git fetch apache
git rebase --onto apache/main $(git merge-base)

Of course you have to check it manually - but this one should take all the
commits you locally committed when you worked on your PR and 'transplant'
them on top of the main branch.

Few things to take care of after:

1. Make sure to rebuild your breeze image:

breeze ci-image build

2. Make sure to resync your uv .venv including reinstallation:

uv self upgrade
uv sync --reinstall

This one will update your venv and make sure it gets reinstalled with the
new packages and all necessary deps for core airflow.

There are quite a few other variants of such sync you should be able to use
from now on:

*Syncing airflow core minimum dev dependencies *

uv sync

This one will (after this change) install airflow core + all optional
dependencies of airflow + all pre installed providers locally (and their
dependencies) . Which means that it should allow to run all `airflow-core`
tests. In theory - we still have few tests in airflow that might require
other providers - to be cleaned up later. I will modify our CI later to
also run using those limited, isolated environments to keep it this way in
the future.

You should be also able to run tests after regular activation of your venv
(. ./.ven/bin/activate) and this is where your IDE should also have your
python interpreter set - but uv has this cool `uv run` feature that allows
you to run any command with automated activation of the venv:

uv run pytest airflow-core/tests/


Also this should work out of the box:

uv run airflow

Go figure :)


*Syncing dependencies for particular provider (and other dependent
providers)*

In the root of Airflow repo

uv sync --package apache-airflow-providers-amazon

This will sync amazon and all necessary development deps + all the
providers that amazon depends on, this way you **should** be able to run
all amazon provider tests (including transfers and all others) - what
Dennis asked about at the call yesterday.

Similarly you can run your tests this way

uv run --package apache-airflow-providers-amazon pytest
providers/amazon/unit/

*Alternative way of syncing provider dependencies *

cd providers/amazon
uv sync

In this case you should be able to also do this:

uv run pytest tests/unit/

You soon will be able to do the same in `airflow-core` - once the tests
that are expecting providers are removed from "airflow-core".

cd airflow-core
uv sync

That's about it. All the rest should not change, Breeze tests,
start-airflow etc. should work as usual.


*Syncing all dependencies*

This is equivalent to what `breeze` image has. I do not really recommend
using it daily - syncing venv and swapping dependencies take sub-seconds
with *uv, *also you should really treat the .venv in your repo as
disposable and something you can easily resync any time.

uv sync --all-packages

This should allow you to run everything

uv run --all-packages pytest 

Have fun!

I am here and on slack `#contributors` later today. Shoot me with any
questions and problems - happy to help (and encourage to help each other
there too)

*Bonus info*

Actually you do not even need to do 'uv sync`. When you use uv run ,
uv automatically
runs uv sync under the hood (applying the --package switches as
appropriate) and you get the latest env resynced automatically !

Actually it's even more - you do not need python installed at all when you
run `uv run` - uv will download and install (in seconds) the right version
of Python for you automatically !

So really:

* Install uv
* git clone
* uv run pytest

Is absolutely all you need to start contributing to Airflow.

And I absolutely love it. This has been 4 years in the making and it's
finally there!

J



On Thu, Mar 20, 2025 at 12:56 PM Jarek Potiuk  wrote:

> Ok. The PR https://github.com/apache/airflow/pull/47798 is "green" (minus
> failing main issue with microsoft libraries solved separately and randomly
> failing k8s tests that we are fighting with).
>
> I also added a description of the changes and happy to take any comments
> and reviews. Would be great to get it merged **right** after the beta
> release, to not disturb the release but also to get as many open PRs as
> possible before the merge to minimize the number of conflicts YOU will have
> to solve (at the expense of ME solving them :) ).
>
> I would like to have a small discussion afterwards on the exact way we
> will treat `uv sync` and dependencies - including pre-installed providers,
> but I woul

[CONTRIBUTOR JOURNEY OPTIMISATION] Improving speed of iteration for doc building (yay!)

[Jarek Potiuk]

Hello.

Another day, another Contributor Journey Optimization improvement.

Just about to get an RC from Airflow, I followed up after all the
restructuring / uv work done and here is one true gem that has been made
possible by that restructuring (or repainting) work -sp improving doc build
iteration speed.

I just completed the docs (in the background of Open Lineage Meetup in
Warsaw) - where I made it super (I think) easy to iterate on our docs.
Something that will be truly needed now - when we likely need to write a
lot of docs for all the new things we created.

Here is hte PR https://github.com/apache/airflow/pull/48760

After this PR is merged, with `uv` and separate distributions and
refactoring and moving the doc code to `devel-common` it's literally as
easy as:

cd devel-common
uv run src/sphinx_exts/docs_build/fetch_inventories.py

This one downloads inventories that documentation links to)

cd /docs
uv run sphinx-autobuild -T --color -b html  . _build

This will (locally - without breeze) open an auto-refreshing web server
with the documentation build (after some initial startup) . With my tests,
it takes a few seconds for a change in your sources to get automatically
(!) refreshed in your browser (both on airflow-core docs and individual
providers docs).

There is one prerequisite (enchant library) that needs to be set-up locally
(but in the docs I explained how to do it on Mac OS especially). The
"contributing-docs" are already updated in my PR to explain what to do.

Here are the possible distributions you can run that sphinx-autobuild
command in.

* ``airflow-core/docs`` - documentation for Airflow Core
* ``providers/**/docs`` - documentation for Providers (90+ folders)
* ``chart/docs`` - documentation for Helm Chart
* ``task-sdk/docs`` - documentation for Task SDK (new format not yet
published)
* ``airflow-ctl/docs`` - documentation for Airflow CLI (future)

Documentation for general overview and summaries not connected with amy
specific distribution:

* ``docker-stack-docs`` - documentation for Docker Stack'
* ``providers-summary-docs`` - documentation for provider summary page

There will likely be some teething issues - but If you would like to check
the PR out and let me know in #documentation slack channel if you see any
issues - we can solve them before or after.

J.

Re: [DISCUSS] confusing alert re SimpleAuthManager

[Vincent Beck]

We could simply stop printing out these passwords. Passwords are auto generated 
if not already defined in a file configured in `[core] 
simple_auth_manager_passwords_file`. So the user can see these passwords by 
opening this file. We could (if it is not considered as unsecured?) print out 
the filename in the stdout so that the user can click on it and see the 
passwords only if some passwords changed.

On 2025/03/21 18:03:19 Jarek Potiuk wrote:
> Well.. Actually Pierre is quite right. While we have not intended Simple
> Auth Manager for production it **could** be used.
> 
> However we would have to carefully think what to do with default passwords
> etc. Currently a lot of warnings in CodeQL were about "writing sensitive
> information to logs" - and a lot of that is about SAM (nice acronym BTW)
> writing the generated passwords to logs and stdout. And I dismissed it as
> "Used in tests" for SAM cases.
> 
> So if we decide to use it, we need to decide how to deal with the password
> generation and default users. We should follow (and this in the future will
> be even mandated by various regulations like CRA) is "secure by default".
> Which means that default installation MUST be secure. Once we solve this, I
> am fine with using SAM in production
> 
> J.
> 
> 
> On Fri, Mar 21, 2025 at 6:27 PM Pierre Jeambrun 
> wrote:
> 
> > Is it really wrong to use the SimpleAuthManager in production ? To my
> > knowledge it lacks a lot of features such as user management and the
> > permission model is really simplistic, but maybe some installations don’t
> > need the fancy Auth stuff ?
> >
> > Instead of being a scary warning that could be just an info block, with
> > details and mention of other Auth Manager in case more use cases need to be
> > supported. (Or link to doc etc)
> >
> > Also we can easily add a “don’t show again” box or something like that,
> > stored on the client side and remove the message if chosen by the user. (Or
> > even a global config setting for all users).
> >
> > On Fri 21 Mar 2025 at 16:03, Vincent Beck  wrote:
> >
> > > This alert can be definitely improved. I do think we should have it and
> > we
> > > should not remove it. If you have some proposals, please feel free to
> > > create a PR, I'll be happy to review. Mentioning the other auth managers
> > as
> > > alternatives is, I think, a great idea.
> > >
> > > On 2025/03/21 07:20:26 Amogh Desai wrote:
> > > > Hmmm, I wonder if it can instead be made clearer. Something like this?
> > > >
> > > > *Simple Auth Manager Enabled.*
> > > > *The Simple Auth Manager is intended for development and testing. If
> > > you're
> > > > using it in production, ensure that access is controlled through other
> > > > means. *
> > > > **
> > > >
> > > > Thanks & Regards,
> > > > Amogh Desai
> > > >
> > > >
> > > > On Thu, Mar 20, 2025 at 11:58 PM Daniel Standish
> > > >  wrote:
> > > >
> > > > > I'm saying, sounds confusing!
> > > > >
> > > > > On Thu, Mar 20, 2025 at 11:27 AM 
> > > wrote:
> > > > >
> > > > > > Sounds great! Do we have something in the config linter to
> > highlight
> > > this
> > > > > > change?
> > > > > >
> > > > > > > On Mar 20, 2025, at 11:19 PM, Daniel Standish
> > > > > >  wrote:
> > > > > > >
> > > > > > > It says this:
> > > > > > >
> > > > > > > Development-only auth manager configured
> > > > > > > The auth manager configured in your environment is the Simple
> > Auth
> > > > > > Manager,
> > > > > > > which is intended for development use only. It is not suitable
> > for
> > > > > > > production and should not be used in a production environment.
> > > > > > >
> > > > > > >> On Thu, Mar 20, 2025 at 10:48 AM Jarek Potiuk  > >
> > > > > wrote:
> > > > > > >>
> > > > > > >> What's the alert - at least for me it did not get through
> > > > > > >>
> > > > > > >> On Thu, Mar 20, 2025 at 6:33 PM Daniel Standish
> > > > > > >>  wrote:
> > > > > > >>
> > > > > > >>> I should add, the import here is, many users who never
> > customized
> > > > > auth
> > > > > > >>> before will now see this message and not really have a clue
> > what
> > > they
> > > > > > are
> > > > > > >>> supposed to do, and I think it will probably create a good
> > > amount of
> > > > > > >>> confusion.
> > > > > > >>>
> > > > > > >>> On Thu, Mar 20, 2025 at 10:27 AM Daniel Standish <
> > > > > > >>> daniel.stand...@astronomer.io> wrote:
> > > > > > >>>
> > > > > >  I just saw this when spinning up airflow
> > > > > > 
> > > > > >  [image: image.png]
> > > > > > 
> > > > > >  I think the message is confusing / misleading / not very
> > > helpful.
> > > > > > 
> > > > > >  There's nothing necessarily wrong with having simple auth or
> > no
> > > auth
> > > > > > if
> > > > > >  you control access some other way.  Moreover we don't tell
> > users
> > > > > what
> > > > > > >> they
> > > > > >  should do instead!
> > > > > > 
> > > > > >  So I think we should either remove this bubble or add more
> > > nuance
> > > > > 

Re: 📢 Apache Airflow 3.0.0beta4 is available for testing! Final beta!! 🎉

[Buğra Öztürk]

Amazing news! Kudos to everyone who contributed and made this happen!

On Thu, Mar 20, 2025 at 9:52 PM Kaxil Naik  wrote:

> Docker image is published, use the following:
>
> docker pull apache/airflow:3.0.0b4
>
> On Fri, 21 Mar 2025 at 01:58, Vikram Koka 
> wrote:
>
> > Awesome!
> >
> > Thank you Kaxil and everyone who contributed to this release!
> >
> > Vikram
> >
> > On Thu, Mar 20, 2025 at 12:55 PM Jarek Potiuk  wrote:
> >
> > > Wowowowowwowow
> > >
> > > On Thu, Mar 20, 2025 at 8:54 PM Kaxil Naik 
> wrote:
> > >
> > > > Dear Airflow Community,
> > > >
> > > > I am thrilled to announce the availability of Apache Airflow
> > 3.0.0.beta4
> > > > for testing!
> > > >
> > > > Airflow 3.0 marks a significant milestone as the first major
> > > > release in over four years, introducing improvements that enhance
> user
> > > > experience, task execution, and system scalability.
> > > >
> > > > First, a few caveats:
> > > >
> > > > This is a beta release, so do not run it in production. It may
> contain
> > > > significant issues, and you will likely need to reset your database
> > > between
> > > > this and subsequent release candidate versions. (Consider yourself
> > > > warned!)
> > > >
> > > > This release is intended for Airflow developers only to test the
> build
> > > and
> > > > start preparing for Airflow 3.0.0. This is not an official
> release—that
> > > > will happen when we create a release candidate and hold a vote. The
> > > > expected timeline for the first release candidate is the week of
> > > > 2025-03-31, but we encourage early feedback to help stabilize the
> > > release.
> > > >
> > > > Where to get it? The beta snapshot is available at:
> > > > https://dist.apache.org/repos/dist/dev/airflow/3.0.0b4
> > > >
> > > >- apache-airflow-3.0.0b3-bin.tar.gz: Binary Python "sdist"
> snapshot.
> > > >- apache_airflow-3.0.0b3-py3-none-any.whl: Binary Python wheel
> > > snapshot.
> > > >
> > > > This snapshot has also been published to PyPI at
> > > > https://pypi.org/project/apache-airflow/3.0.0b4/
> > > >
> > > > Also present are beta releases for various other packages which you
> > might
> > > > also need for 3.0.0b4 to work. These have also been published to
> PyPI.:
> > > >
> > > >- apache-airflow-task-sdk
> > > >- apache-airflow-providers-celery
> > > >- apache-airflow-providers-cncf-kubernetes
> > > >- apache-airflow-providers-common-compat
> > > >- apache-airflow-providers-common-io
> > > >- apache-airflow-providers-common-messaging
> > > >- apache-airflow-providers-common-sql
> > > >- apache-airflow-providers-fab
> > > >- apache-airflow-providers-openlineage
> > > >- apache-airflow-providers-standard
> > > >
> > > >
> > > >
> > > > *Public Keys & Verification*
> > > >
> > > > Public keys for verification are available at:
> > > > https://www.apache.org/dist/airflow/KEYS
> > > >
> > > > Jed has signed the artifacts.
> > > >
> > > > *Instructions*:
> > > >
> > > > You can build a virtualenv that installs this beta, and other
> required
> > > > packages (e.g. task sdk), like this:
> > > >
> > > > ```
> > > > uv venv
> > > >
> > > > uv pip install \
> > > > apache-airflow==3.0.0b4 \
> > > > apache-airflow-providers-celery==3.10.4b1 \
> > > > apache-airflow-providers-cncf-kubernetes==10.4.0b1 \
> > > > apache-airflow-providers-common-compat==1.6.0b1 \
> > > > apache-airflow-providers-common-io==1.5.2b1 \
> > > > apache-airflow-providers-common-sql==1.24.1b1 \
> > > > apache-airflow-providers-fab==2.0.0b1 \
> > > > apache-airflow-providers-openlineage==2.1.2b1 \
> > > > apache-airflow-providers-standard==0.2.0b1 \
> > > > apache-airflow-task-sdk==1.0.0b4
> > > > ```
> > > >
> > > > The Dockerfiles will also be published in an hour. Once they are
> done,
> > I
> > > > will reply to this email.
> > > >
> > > >
> > > > *What's new in Airflow 3?*
> > > > Airflow 3.0.0 introduces significant enhancements and breaking
> changes.
> > > >
> > > > Notable Features
> > > >
> > > > DAG versioning & Bundles
> > > >
> > > > Airflow now tracks DAG versions, offering better visibility into
> > > historical
> > > > DAG changes and execution states. The introduction of DAG Bundles
> > ensures
> > > > tasks run with the correct code version, even as DAGs evolve.
> > > >
> > > > Modern Web Application
> > > >
> > > > The UI has been rebuilt using React and a complete API-driven
> > structure,
> > > > improving maintainability and extensibility. It includes a new
> > > > component-based design system and an enhanced information
> > architecture. A
> > > > new React-based plugin system supports custom widgets, improved
> > workflow
> > > > visibility, and integration with external tools.
> > > >
> > > > Task Execution Interface
> > > >
> > > > Airflow 3.0 adopts a client / server architecture, decoupling task
> > > > execution from the internal meta-database via API-based interaction.
> > This
> > > > allows for remote execution a

Re: New committer: Rahul Vats

[Ephraim Anierobi]

Congratulations Rahul! Well deserved

On Tue, 1 Apr 2025 at 01:27, Pierre Jeambrun  wrote:

> Amazing work Rahul, congratulations.
>
> On Mon 31 Mar 2025 at 23:14, Pavankumar Gopidesu 
> wrote:
>
> > Woohoo, Congratulations Rahul 🎉🎉
> >
> > Pavan.
> >
> > On Mon, Mar 31, 2025 at 9:17 PM Pankaj Koti
> >  wrote:
> >
> > > Many congratulations Rahul! Very happy for you and well deserved 🎉🎉
> > >
> > > On Tue, 1 Apr, 2025, 01:17 Buğra Öztürk, 
> > wrote:
> > >
> > > > Amazing news! Congratulations Rahul! Well deserved!
> > > >
> > > > On Mon, Mar 31, 2025 at 9:14 PM Vincent Beck 
> > > wrote:
> > > >
> > > > > Congrats Rahul! Very well deserved!
> > > > >
> > > > > On 2025/03/31 19:08:09 Shubham Raj wrote:
> > > > > > Congrats Rahul, well deserved!!
> > > > > >
> > > > > > On Tue, 1 Apr 2025 at 00:33, Vishnu Chilukoori <
> > > > > vish.chiluko...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Congrats Rahul...well deserved!!
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Vishnu Chilukoori
> > > > > > >
> > > > > > > On Mon, Mar 31, 2025 at 11:53 AM Idris Adebisi
> > > > > > >  wrote:
> > > > > > >
> > > > > > > >  Congratulations, Rahul!
> > > > > > > >
> > > > > > > > On Monday, March 31, 2025 at 07:45:27 PM GMT+1, Ambika
> > Garg <
> > > > > > > > ambikagarg1...@gmail.com> wrote:
> > > > > > > >
> > > > > > > >  Congratulations Rahul!!
> > > > > > > > On Mon, Mar 31, 2025 at 2:43 PM Ankit Chaurasia <
> > > > sunank...@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Congratulations, Rahul! Well deserved.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, Apr 1, 2025 at 12:16 AM Constance Martineau
> > > > > > > > >  wrote:
> > > > > > > > >
> > > > > > > > > > Congrats Rahul! Well deserved :)
> > > > > > > > > >
> > > > > > > > > > On Mon, Mar 31, 2025 at 2:28 PM Oliveira, Niko
> > > > > > > > >  > > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Congrats Rahul, great work!
> > > > > > > > > > >
> > > > > > > > > > > 
> > > > > > > > > > > From: Jed Cunningham 
> > > > > > > > > > > Sent: Monday, March 31, 2025 11:19:53 AM
> > > > > > > > > > > To: dev@airflow.apache.org
> > > > > > > > > > > Subject: [EXT] New committer: Rahul Vats
> > > > > > > > > > >
> > > > > > > > > > > CAUTION: This email originated from outside of the
> > > > > organization. Do
> > > > > > > > not
> > > > > > > > > > > click links or open attachments unless you can confirm
> > the
> > > > > sender
> > > > > > > and
> > > > > > > > > > know
> > > > > > > > > > > the content is safe.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > AVERTISSEMENT: Ce courrier électronique provient d’un
> > > > > expéditeur
> > > > > > > > > externe.
> > > > > > > > > > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce
> jointe
> > > si
> > > > > vous
> > > > > > > ne
> > > > > > > > > > pouvez
> > > > > > > > > > > pas confirmer l’identité de l’expéditeur et si vous
> > n’êtes
> > > > pas
> > > > > > > > certain
> > > > > > > > > > que
> > > > > > > > > > > le contenu ne présente aucun risque.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > The Project Management Committee (PMC) for Apache
> Airflow
> > > > > > > > > > > has invited Rahul Vats to become a committer and we are
> > > > pleased
> > > > > > > > > > > to announce that they have accepted.
> > > > > > > > > > >
> > > > > > > > > > > Please join us in welcoming Rahul to their new role and
> > > > > > > > > > > responsibility in our project community.
> > > > > > > > > > >
> > > > > > > > > > > Rahul has had a tremendous impact on Airflow 3,
> primarily
> > > > > around
> > > > > > > > > testing.
> > > > > > > > > > > Thanks Rahul, welcome, it's well deserved!
> > > > > > > > > > >
> > > > > > > > > > > Jed
> > > > > > > > > > > On behalf of the Apache Airflow PMC
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > > > >
> > > > >
> > > >
> > > > --
> > > > Bugra Ozturk
> > > >
> > >
> >
>

Re: 📢 Apache Airflow 3.0.0beta4 is available for testing! Final beta!! 🎉

[Vikram Koka]

Awesome!

Thank you Kaxil and everyone who contributed to this release!

Vikram

On Thu, Mar 20, 2025 at 12:55 PM Jarek Potiuk  wrote:

> Wowowowowwowow
>
> On Thu, Mar 20, 2025 at 8:54 PM Kaxil Naik  wrote:
>
> > Dear Airflow Community,
> >
> > I am thrilled to announce the availability of Apache Airflow 3.0.0.beta4
> > for testing!
> >
> > Airflow 3.0 marks a significant milestone as the first major
> > release in over four years, introducing improvements that enhance user
> > experience, task execution, and system scalability.
> >
> > First, a few caveats:
> >
> > This is a beta release, so do not run it in production. It may contain
> > significant issues, and you will likely need to reset your database
> between
> > this and subsequent release candidate versions. (Consider yourself
> > warned!)
> >
> > This release is intended for Airflow developers only to test the build
> and
> > start preparing for Airflow 3.0.0. This is not an official release—that
> > will happen when we create a release candidate and hold a vote. The
> > expected timeline for the first release candidate is the week of
> > 2025-03-31, but we encourage early feedback to help stabilize the
> release.
> >
> > Where to get it? The beta snapshot is available at:
> > https://dist.apache.org/repos/dist/dev/airflow/3.0.0b4
> >
> >- apache-airflow-3.0.0b3-bin.tar.gz: Binary Python "sdist" snapshot.
> >- apache_airflow-3.0.0b3-py3-none-any.whl: Binary Python wheel
> snapshot.
> >
> > This snapshot has also been published to PyPI at
> > https://pypi.org/project/apache-airflow/3.0.0b4/
> >
> > Also present are beta releases for various other packages which you might
> > also need for 3.0.0b4 to work. These have also been published to PyPI.:
> >
> >- apache-airflow-task-sdk
> >- apache-airflow-providers-celery
> >- apache-airflow-providers-cncf-kubernetes
> >- apache-airflow-providers-common-compat
> >- apache-airflow-providers-common-io
> >- apache-airflow-providers-common-messaging
> >- apache-airflow-providers-common-sql
> >- apache-airflow-providers-fab
> >- apache-airflow-providers-openlineage
> >- apache-airflow-providers-standard
> >
> >
> >
> > *Public Keys & Verification*
> >
> > Public keys for verification are available at:
> > https://www.apache.org/dist/airflow/KEYS
> >
> > Jed has signed the artifacts.
> >
> > *Instructions*:
> >
> > You can build a virtualenv that installs this beta, and other required
> > packages (e.g. task sdk), like this:
> >
> > ```
> > uv venv
> >
> > uv pip install \
> > apache-airflow==3.0.0b4 \
> > apache-airflow-providers-celery==3.10.4b1 \
> > apache-airflow-providers-cncf-kubernetes==10.4.0b1 \
> > apache-airflow-providers-common-compat==1.6.0b1 \
> > apache-airflow-providers-common-io==1.5.2b1 \
> > apache-airflow-providers-common-sql==1.24.1b1 \
> > apache-airflow-providers-fab==2.0.0b1 \
> > apache-airflow-providers-openlineage==2.1.2b1 \
> > apache-airflow-providers-standard==0.2.0b1 \
> > apache-airflow-task-sdk==1.0.0b4
> > ```
> >
> > The Dockerfiles will also be published in an hour. Once they are done, I
> > will reply to this email.
> >
> >
> > *What's new in Airflow 3?*
> > Airflow 3.0.0 introduces significant enhancements and breaking changes.
> >
> > Notable Features
> >
> > DAG versioning & Bundles
> >
> > Airflow now tracks DAG versions, offering better visibility into
> historical
> > DAG changes and execution states. The introduction of DAG Bundles ensures
> > tasks run with the correct code version, even as DAGs evolve.
> >
> > Modern Web Application
> >
> > The UI has been rebuilt using React and a complete API-driven structure,
> > improving maintainability and extensibility. It includes a new
> > component-based design system and an enhanced information architecture. A
> > new React-based plugin system supports custom widgets, improved workflow
> > visibility, and integration with external tools.
> >
> > Task Execution Interface
> >
> > Airflow 3.0 adopts a client / server architecture, decoupling task
> > execution from the internal meta-database via API-based interaction. This
> > allows for remote execution across networks, multi-language support,
> > enhanced security, and better dependency management. The Edge Executor
> > further enables seamless remote task execution without direct database
> > connections.
> >
> > Data Assets & Asset-Centric Syntax
> >
> > Airflow 3.0 enhances dataset management by introducing Data Assets,
> > expanding beyond tables and files to include ML models and more. Assets
> can
> > be explicitly defined using the @asset decorator, simplifying tracking
> and
> > dependencies.
> >
> > External Event-Driven Scheduling
> >
> > Airflow now supports event-driven DAG triggers from external sources like
> > message queues and blob stores. This builds upon dataset scheduling and
> > enhances integration with the external data ecosystem.
> >
> > For a more comprehensiv