Use SimpleAuthManager for standalone #48036
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Should we remove the big scary warning for this use case do you think? |
ashb
approved these changes
Mar 21, 2025
pierrejeambrun
approved these changes
Mar 21, 2025
ephraimbuddy
approved these changes
Mar 21, 2025
This fixes the standalone command. At the same time, it switches standalone to use SimpleAuthManager. Similar to before, if it's the first time you run, the username and password will be printed out - now just at the very top of the output (which honestly is a bit easier to see before a ton of lines start flying by). However, it will only output the password once. On subsequent starts, it will print the file that contains the file so you can go grab the password yourself if you need it. This was done since there isn't an easy way to both use the same password with standalone and api-server directly and make sure we aren't outputting a password you've populated yourself.
vincbeck
approved these changes
Mar 21, 2025
Member
Author
We can't today, unfortunately. But it probably should be toggle-able. If we do though, should be in a follow up. |
If we have all_admins, what folks configure for users doesn't matter.
jedcunningham
force-pushed
the
fix_standalone
branch
from
bc1e4ef to
dd45362
Compare
agupta01
pushed a commit
to agupta01/airflow
that referenced
this pull request
Mar 21, 2025
This fixes the standalone command. At the same time, it switches standalone to use SimpleAuthManager. Similar to before, if it's the first time you run, the username and password will be printed out - now just at the very top of the output (which honestly is a bit easier to see before a ton of lines start flying by). However, it will only output the password once. On subsequent starts, it will print the file that contains the file so you can go grab the password yourself if you need it. This was done since there isn't an easy way to both use the same password with standalone and api-server directly and make sure we aren't outputting a password you've populated yourself.
Member
|
Nice! |
shubham-pyc
pushed a commit
to shubham-pyc/airflow
that referenced
this pull request
Mar 22, 2025
This fixes the standalone command. At the same time, it switches standalone to use SimpleAuthManager. Similar to before, if it's the first time you run, the username and password will be printed out - now just at the very top of the output (which honestly is a bit easier to see before a ton of lines start flying by). However, it will only output the password once. On subsequent starts, it will print the file that contains the file so you can go grab the password yourself if you need it. This was done since there isn't an easy way to both use the same password with standalone and api-server directly and make sure we aren't outputting a password you've populated yourself.
2 tasks
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
Apr 4, 2025
This fixes the standalone command. At the same time, it switches standalone to use SimpleAuthManager. Similar to before, if it's the first time you run, the username and password will be printed out - now just at the very top of the output (which honestly is a bit easier to see before a ton of lines start flying by). However, it will only output the password once. On subsequent starts, it will print the file that contains the file so you can go grab the password yourself if you need it. This was done since there isn't an easy way to both use the same password with standalone and api-server directly and make sure we aren't outputting a password you've populated yourself.
This was referenced Apr 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the standalone command.
At the same time, it switches standalone to use SimpleAuthManager (and forces the use of standalone!).
Similar to before, if it's the first time you run, the username and password will be printed out - now just at the very top of the output (which honestly is a bit easier to see before a ton of lines start
flying by). However, it will only output the password once. On
subsequent starts, it will print the file that contains the file so you can go grab the password yourself if you need it. This was done since there isn't a trivial way to both use the same password with standalone and api-server directly and make sure we aren't outputting a password you've populated yourself.
On a fresh start:
On a subsequent start: