Splitting syspath preparation into stages #41672
Merged
Conversation
This file contains 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
potiuk
approved these changes
Aug 22, 2024
|
a test needs fixing |
|
Still a test failing |
uranusjr
approved these changes
Aug 23, 2024
|
This one should also be backported to 2.10.1 |
uranusjr
pushed a commit
to astronomer/airflow
that referenced
this pull request
Aug 23, 2024
amoghrajesh
added a commit
to amoghrajesh/airflow
that referenced
this pull request
Aug 23, 2024
(cherry picked from commit 0be5dec)
potiuk
pushed a commit
that referenced
this pull request
Aug 23, 2024
utkarsharma2
pushed a commit
that referenced
this pull request
Sep 2, 2024
23 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Splitting the airflow/settings.py#initialize into stages for easier maintainability.
^ 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.rstor{issue_number}.significant.rst, in newsfragments.