Skip to content

Fix airflow config lint staying silent on conditional removal rules - #70977

Open
Eason09053360 wants to merge 1 commit into
apache:mainfrom
Eason09053360:fix-config-lint-remove-if-equals
Open

Fix airflow config lint staying silent on conditional removal rules#70977
Eason09053360 wants to merge 1 commit into
apache:mainfrom
Eason09053360:fix-config-lint-remove-if-equals

Conversation

@Eason09053360

Copy link
Copy Markdown
Contributor

airflow config lint never reported the removal rules marked with remove_if_equals . The marker was treated as a reason to skip the rule entirely, so the current value was never compared against it and lint printed "No issues found" regardless. Five rules were affected, three of them breaking.

Same fix as #66370, which corrected the parallel ConfigChange in airflow-ctl but left the core CLI behind.


Was generative AI tooling used to co-author this PR?

  • Yes — Claude Code (Opus 5)
    Generated-by: Claude Code (Opus 5) following the guidelines

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {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.

Config changes that are only removed for one specific value carry a
remove_if_equals marker. Lint treated the presence of that marker as a
reason to say nothing at all, so users upgrading with any of the five
affected settings -- including three breaking ones -- were told their
configuration was ready for Airflow 3 and only discovered otherwise
after the upgrade broke.

Because the marker was tested for truthiness rather than for being
unset, a rule keyed to an empty string was also reported unconditionally,
warning about configurations that were in fact fine.

airflowctl already resolved this in apache#66370; this brings the core CLI in
line with the behaviour that command has shipped since.
@Eason09053360
Eason09053360 marked this pull request as ready for review August 3, 2026 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant