Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Aug 10, 2025

…mands (#54325)

The --auth-manager was only defined for "start-airflow" command so far, and you had to use it every time you wanted to swith to non-default Auth Manager (FabAuthManager). This was not very convenient when you wanted to test things with breeze shell and keep it configured between sessions.

After this change:

  • turns --auth-manager into "CacheableChoice" flag - where last used value is cached in .build folder and reused next time automatically

  • the flag is now present in those commands:

    • start-airflow
    • breeze shell
    • breeze
  • You can configure auth manager and change the cached value via breeze setup config command - like python/backend etc.

(cherry picked from commit 2770924)


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…mands (apache#54325)

The `--auth-manager` was only defined for "start-airflow" command so far,
and you had to use it every time you wanted to swith to non-default Auth Manager
(FabAuthManager). This was not very convenient when you wanted to test things
with breeze shell and keep it configured between sessions.

After this change:

* turns --auth-manager into "CacheableChoice" flag - where last used
  value is cached in .build folder and reused next time automatically

* the flag is now present in those commands:

  * start-airflow
  * breeze shell
  * breeze

* You can configure auth manager and change the cached value via
  `breeze setup config` command - like python/backend etc.

(cherry picked from commit 2770924)
@potiuk potiuk merged commit 15da8f7 into apache:v3-0-test Aug 10, 2025
8 checks passed
@potiuk potiuk deleted the backport-2770924-v3-0-test branch August 10, 2025 21:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant