Conversation
|
Hi maintainer, this PR was merged without a milestone set.
|
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 645413b v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
(cherry picked from commit 645413b) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
I noticed while testing 3.2.0 with helm chart <=1.19.0 that the auto-templates env AIRFLOW__CORE__SQL_ALCHEMY_CONN is not masked. This is not happening in Chart 1.20++ but if you have not upgraded and Airflow 3.0.0 is used with
expose_config: non-sensitive-only(or True) then the db credentials from the legacy key are not masked/visible.This PR adds it to the list of sensitive values.. with the trade-off that implicitly the legacy options gets supported. If wanted I can alternatively implement a more complex option as well which adds another masking list for non-supported legacy values.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.