-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add airflow config lint
cli command for lint the configuration changes from Airflow 2.x to Airflow 3.0
#44908
Conversation
cbc6eab
to
f5b1798
Compare
f5b1798
to
6800d94
Compare
NAAAAJS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, looks really nice!
@sunank200 one comment but thats just a thought. Will it also be possible to add a short README or so in order for someone to deprecate any future options? (Although i think all are done)
6800d94
to
2a9f820
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome :)
Readme for in how to deprecate options in future? @amoghrajesh can you elaborate on this, please |
41b5498
to
b3abb24
Compare
Yeah, that is what I was hinting at. But looking at the state of this PR, it is a good example for how to do it later in future. So I wouldnt ask for that anymore |
re: The README topic, I feel at least we should introduce a news fragment on this. We should probably add a page in documentation that guides people through the migrations. This would be useful for us in blogposts and discussions on Airflow 2-to-3 upgrade path. (This should be a separate PR.) |
fba9885
to
15fe43b
Compare
one test case failed |
It was from different section and fixed it now. |
95a6ab5
to
913b8a7
Compare
d53876a
to
069b1b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, looks good. Left 2 nits. I'm planning on merging it later tonight unless anyone wants to take a deeper look
da3edb2
to
3b50ab4
Compare
c5f8519
to
6218af9
Compare
@sunank200 One discussion has not yet been resolved. Could you please check whether that has been addressed? If so, I'll merge it. Thanks! |
6218af9
to
cd9cb4d
Compare
… changes from Airflow 2.x to Airflow 3.0
Add newsfragments
rename newfragment as feature
cd9cb4d
to
75f95ca
Compare
Backport failed to create: v2-10-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker bc813c6 v2-10-test This should apply the commit to the v2-10-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 --continue |
This PR introduces the
airflow config lint
command as part of the Airflow CLI config commands for migration tooling for Airflow 3.0. The purpose of this command is to help users transition from Airflow 2.x to 3.0 by identifying and providing actionable feedback on removed and renamed configuration parameters.Implementation details:
CLI Usage Examples:
Lint all sections and options:
Lint a specific sections:
Lint a specific sections and options:
Ignore a specific sections during linting:
Ignore a specific options during linting:
Enable verbose output for detailed feedback:
Following is the screenshot of the command used:
closes: #44555
related: #41641
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.