Add integration tests for config sensitive masking in airflowctl #61105
+110
−0
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.
Description
Added integration tests to verify sensitive config values are properly masked end-to-end when using airflowctl with actual Airflow API.
The Airflow API masks sensitive values (like
fernet_key,sql_alchemy_conn) as< hidden >. These integration tests confirm that airflowctl correctly preserves and displays those masked values in real scenarios.Changes
config listcommandconfig getforfernet_keyconfig getforsql_alchemy_conn< hidden >appears in output for sensitive configsRelated PRs
Related Issue
Closes #59843
Testing
# Run from airflow-ctl-tests directory pytest tests/airflowctl_tests/test_config_sensitive_masking.py -v