Respect deprecated options in default config parser #61289
+129
−27
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.
Why
Previously, the default value parser logic in
AirflowConfigParserdid not check forversion_deprecatedordeprecation_reasonfor defaultconfig.yamlThis means that if we really deprecated a
[config/key], like the case of #56150 (comment) (not renaming or moving to other section like AF2 -to AF3), theconf.getwill still get default value from theconfig.yaml.From my perspective, the default value parser should respect deprecated options (the option that provide either
version_deprecatedordeprecation_reason) and ignore it.What
configure_parser_from_configuration_descriptionlogic to shared libWas generative AI tooling used to co-author this PR?
Generated-by: Copilot (ChatGPT 4.1), Gemini-CLI (auto model) following the guidelines