Fix validate_version_added_fields_in_config.py #30181
Merged
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
pierrejeambrun
requested review from
ashb,
jedcunningham and
potiuk
as code owners
potiuk
approved these changes
Mar 18, 2023
ephraimbuddy
approved these changes
Mar 19, 2023
pierrejeambrun
deleted the
fix-validate-version-added-fields-in-config-script
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This fixes
validate_version_added_fields_in_config.py.Following the format update of
airflow/config_templates/config.ymlin #28417, local parsing of the config will fail. (and also future config after the PR is merged)This extends the current behavior to allow old and new config.yml parsing to find
options. (also for future releases, > 2.6.0) Also handles("core", "mp_start_method", "2.5.1"), cf comments.