CLI: secure connection commands by masking sensitive values #60014
+54
−26
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
potiuk
approved these changes
Jan 1, 2026
Member
|
This looks good but the airflow submodule should be removed -> it causes CI failure. Not sure why you had airflow submodule and added it ? |
Author
|
Thanks for catching this 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What does this PR do?
This PR updates the Airflow CLI connection commands to hide connection values by default and redact sensitive fields such as passwords, tokens, and secrets.
Why is this needed?
Exposing connection values via the CLI can leak sensitive information. This change aligns with Airflow’s security best practices and prevents accidental disclosure of secrets.
What was changed?
How was this tested?
Related to #59842